Paste your MCP server's tools/list output, validate against the protocol spec, simulate a tool call without any LLM cost.
Tool schemas
Paste either a full tools/list response (with tools: [...]) or a raw array of tool definitions.
Tool args are validated against the tool's inputSchema. This simulates the JSON-Schema check an MCP server would do before invoking the tool function.
What the LLM sees
This is the actual JSON formatted as it would appear in an LLM's tool-use context. Token estimate uses ~4 chars/token.
— tokens
Validation
—
Paste tools to validate
Findings
Call result
—
As-is, no warranty. These apps are free under their listed license and run entirely in your browser. Use at your own risk — don't blame me if your PC catches fire, your dog runs away, or the math turns out wrong. Verify anything that actually matters. None of this is professional financial, medical, legal, or engineering advice.
The Model Context Protocol (MCP) is the standard for exposing tools to LLMs (Anthropic’s Claude Code, Cursor, Continue, and many other clients use it). MCP servers ship tools whose schemas the LLM reads to decide when and how to call them. Bad schemas = bad tool selection = burned tokens.
This tool catches schema issues before they ship:
tools/list response (or just an array of tools)tools/call to verify arguments validate against your inputSchemaSpec requirements (errors):
name fieldinputSchema fieldinputSchema.type must be "object"Best practices (warnings):
[a-zA-Z0-9_-] (some clients restrict)description (LLM tool selection works better with detailed descriptions)description (argument purpose unclear)type (LLMs may guess wrong)Pick a tool from the dropdown - the tool auto-generates a starter argument stub from your schema. Edit the JSON, watch the validator catch violations in real time:
"5" where "integer" was expected)"meters" not in ["imperial", "metric"])limit: 30 when maximum: 20)This is the same JSON-Schema check your server probably does in code - run it in the browser before round-tripping through an actual LLM.
The tool also shows you the exact JSON your tools become in the LLM’s context window, formatted as the major clients format it. The token estimate is your per-request cost when the tools are loaded (use Prompt Cache Optimizer to see if you can cache them).
For informational purposes only. Not financial, medical, or legal advice. You are solely responsible for how you use these tools.