MCP JSON Validator
Validate MCP tool JSON shapes.
About this tool
Paste MCP tool definitions and check that each has a name and an input schema of the right shape. Errors point to the tool by index, such as tools[1].name: required string. It is a basic shape check, not a full protocol validator.
How to use
How it works
For every tool the validator requires a non-empty string name, a string description if one is present, and an inputSchema (or parameters) that is an object. If the schema has a type, it must be "object". An empty array is reported as an error. It does not validate the JSON Schema inside, annotations or output schemas.
Worked example
Two broken tools
- Input
- [{"name":"get_weather","inputSchema":{"type":"array"}},{"description":"x"}]
- Output
- { "valid": false, "errors": [ "tools[0].inputSchema.type: should be \"object\"", "tools[1].name: required string", "tools[1].inputSchema: required" ], "summary": "2 tool definition(s)" }
- Walkthrough
- The first tool has an array schema where MCP expects an object, and the second has no name or schema.
Limitations
- Checks name, description type and inputSchema shape only.
- Does not validate the contents of inputSchema as JSON Schema.
- Does not check the protocol handshake or run the tool.
Questions
How do I validate an MCP tool definition?
Must inputSchema.type be object?
Does it accept parameters instead of inputSchema?
Does it test the tool against a server?
Features
- Indexed error paths
- Single tool or list
- Runs in your browser
Related resources
Guides and videos from around the web—opens on YouTube or the publisher’s site.
Machine Learning for Everybody
freeCodeCamp.org
Accessible ML survey for AI calculator and metric tools.
Watch on YouTubeBig-O Notation in 100 Seconds
Fireship
Complexity intuition when estimating training/inference cost.
Watch on YouTube
- DeepLearning.AI
DeepLearning.AI
Courses and explainers for modern AI tooling.
- Hugging Face docs
Hugging Face
Model hub docs next to tokenizer and embedding helpers.