Every list entry is a tool object with a name
Each entry of the tools array in a tools/list result is a tool object identified by a string name, with an inputSchema; an entry that is not an object or has no name cannot be called.
Check spec-tool-shape · MCP specification 2026-07-28 · default severity: blocking · rubric 2.1.0
What fails
An entry that is not an object, or has no string name, cannot be called. Clients drop it or fail on the whole list.
The rule
Each tool is uniquely identified by a name and includes metadata describing its schema.
How to fix it
Give every entry a string "name", or remove the entry.
- Make sure tools is an array of objects, each with a string "name" and an "inputSchema".
- Remove placeholder or null entries left by conditional registration.
- Let the SDK build the list rather than assembling JSON by hand.
TypeScript SDK
import { McpServer } from '@modelcontextprotocol/server';
import * as z from 'zod';
const server = new McpServer({ name: 'issues', version: '1.0.0' });
server.registerTool(
'get_issue',
{
title: 'Get issue',
description: 'Return one issue by ID. Use when the user names an issue.',
inputSchema: z.strictObject({
issue_id: z.string().describe('Issue ID, for example ISS-42'),
}),
annotations: { readOnlyHint: true, destructiveHint: false, openWorldHint: false },
},
async ({ issue_id }) => ({ content: [{ type: 'text', text: 'Done' }] }),
);Python SDK
from typing import Annotated
from pydantic import Field
from mcp.server.mcpserver import MCPServer
from mcp.types import ToolAnnotations
server = MCPServer("issues")
@server.tool(
title="Get issue",
annotations=ToolAnnotations(readOnlyHint=True, destructiveHint=False, openWorldHint=False),
)
def get_issue(
issue_id: Annotated[str, Field(description="Issue ID, for example ISS-42")],
) -> str:
"""Return one issue by ID. Use when the user names an issue."""
return "Done"Run against @modelcontextprotocol/server 2.4.0, mcp 2.3.0 and fastmcp 4.2.2 on 2026-11-18; the checker confirms this check passes on the tool list each snippet produces.
Questions
What does a minimal valid tool look like?
{"name": "get_time", "description": "Returns the server time.", "inputSchema": {"type": "object"}}. Directories also expect a title and annotations.
How do I see my server’s tools/list answer?
Run npx @modelcontextprotocol/inspector --cli <server> --method tools/list and save the output; paste it into the checker.
Related checks
- inputSchema is present
- Tool fields have the types the schema defines
- The paste holds the whole tool list
- All checks in MCP specification 2026-07-28: tools/list rules
Further reading
How this check is graded
It counts toward: MCP specification 2026-07-28. See the rubric.
Last verified against MCP specification 2026-07-28: Tools on 2026-11-18. The rule above is quoted in the source’s own words. This page as Markdown.
Check your tool list: paste your tools/list, nothing is sent anywhere