inputSchema is present
inputSchema is a required field of every MCP tool and must be a JSON Schema object, not null; a tool with no arguments uses {"type": "object", "additionalProperties": false}.
Check spec-input-schema-missing · MCP specification 2026-07-28 · default severity: blocking · rubric 2.1.0
Error message you’ll see
tools.0.custom.input_schema.type: Field requiredClaude API (400), when the root has no "type": "object". Where this was reported
What fails
inputSchema is a required field of a tool. Without it, clients cannot build or validate the arguments.
The rule
MUST be a valid JSON Schema object (not
null)
How to fix it
Add an inputSchema. A tool with no arguments uses {"type": "object", "additionalProperties": false}.
- Add an inputSchema to every tool the server lists.
- For a tool without arguments, use {"type": "object", "additionalProperties": false}.
- With an SDK, pass an empty object schema rather than leaving the field out.
{ "name": "get_time", "description": "Returns the server time." }{ "name": "get_time", "description": "Returns the server time.", "inputSchema": { "type": "object", "additionalProperties": false } }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_server_time',
{
title: 'Get server time',
description: 'Return the current server time in UTC. Use when the user asks what time the service uses.',
inputSchema: z.strictObject({}),
annotations: { readOnlyHint: true, destructiveHint: false, openWorldHint: false },
},
async () => ({ 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 server time",
annotations=ToolAnnotations(readOnlyHint=True, destructiveHint=False, openWorldHint=False),
)
def get_server_time() -> str:
"""Return the current server time in UTC. Use when the user asks what time the service uses."""
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 inputSchema should a tool without arguments have?
{"type": "object", "additionalProperties": false}. It says the tool takes an empty object and nothing else. Both SDKs emit it from an empty argument list.
Is inputSchema: null allowed?
No. The specification says it MUST be a valid JSON Schema object, not null.
Related checks
- inputSchema has type "object" at the root
- The schema field is named inputSchema
- inputSchema and outputSchema are valid JSON Schema
- All checks in MCP tool input and output schemas
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