# 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. Last verified against MCP specification 2026-07-28: Tools on 2026-11-18.

## 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.

Source: [MCP specification 2026-07-28: Tools](https://modelcontextprotocol.io/specification/2026-07-28/server/tools)

## How to fix it

Give every entry a string "name", or remove the entry.

1. Make sure tools is an array of objects, each with a string "name" and an "inputSchema".
2. Remove placeholder or null entries left by conditional registration.
3. Let the SDK build the list rather than assembling JSON by hand.

### TypeScript SDK

```ts
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

```python
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"
```

## 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](https://isokron.ai/mcp-check/checks/spec-input-schema-missing)
- [Tool fields have the types the schema defines](https://isokron.ai/mcp-check/checks/spec-field-types)
- [The paste holds the whole tool list](https://isokron.ai/mcp-check/checks/spec-pagination-partial)
- [MCP specification 2026-07-28: tools/list rules](https://isokron.ai/mcp-check/checks/protocol)

## Further reading

- [How to test an MCP server without fooling yourself](https://isokron.ai/research/how-to-test-an-mcp-server)

Counts toward: MCP specification 2026-07-28.

Rubric: https://isokron.ai/mcp-check/rubric

Check your tool list: https://isokron.ai/mcp-check
