# The schema field is named inputSchema

**In MCP the field is inputSchema; input_schema is the spelling of model APIs such as Anthropic’s Messages API, so an MCP client that receives input_schema treats the tool as having no schema.**

Check `spec-input-schema-field-name` · MCP specification 2026-07-28 · default severity: attention · rubric 2.1.0. Last verified against MCP specification 2026-07-28: Tools on 2026-11-18.

## What fails

The tool uses input_schema, the spelling of some model APIs. MCP clients read inputSchema, so they see no schema. If you pasted a converted list, ignore this item.

## The rule

> MUST be a valid JSON Schema object (not `null`)

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

## How to fix it

Rename input_schema to inputSchema in what the server returns from tools/list.

1. Rename input_schema to inputSchema in what the server returns from tools/list.
2. If you pasted a list converted for a model API, ignore this finding: the server itself is what counts.
3. Let the SDK build the definition instead of writing tool 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

### Why do some examples use input_schema?

The Claude Messages API and some agent frameworks call the field input_schema. Clients convert inputSchema to it before calling the model; a server must use the MCP spelling.

### Will clients accept both?

Not reliably. Most read only inputSchema and either drop the tool or call it with no arguments.

## Related checks

- [inputSchema is present](https://isokron.ai/mcp-check/checks/spec-input-schema-missing)
- [inputSchema has type "object" at the root](https://isokron.ai/mcp-check/checks/spec-input-schema-root-object)
- [Tool fields have the types the schema defines](https://isokron.ai/mcp-check/checks/spec-field-types)
- [MCP tool input and output schemas](https://isokron.ai/mcp-check/checks/schema)

Counts toward: MCP specification 2026-07-28.

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

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