MCP tools/list Inspector
🔒 In your browserInspect & validate an MCP tools/list response — params, required fields & schema issues.
How it works
Paste a server's tools/list response (or any Anthropic/OpenAI tools array) to get a readable breakdown of every tool, its parameters and required fields — plus lint warnings for missing descriptions, bad schemas and duplicates. Runs entirely in your browser.
Structural review only — it can't tell whether a tool does what its description claims. To check a server for hidden or malicious instructions, use the MCP Security Scanner. Nothing is uploaded.
About the MCP tools/list Inspector
An MCP server advertises what it can do through a tools/list response — a JSON array of tools, each with a name, description and input schema. This free MCP tools/list inspector turns that raw JSON into a readable summary of every tool and its parameters, and flags schema problems that can stop a client from using a tool.
Everything is parsed in your browser; the JSON you paste is never uploaded.
What you get
- A clean list of every tool with its description and parameters.
- Each parameter's type and whether it's required, at a glance.
- Lint warnings: missing names or descriptions, non-object schemas, duplicate tools, and required fields not present in properties.
What it accepts
Paste a full JSON-RPC tools/list result, a plain { "tools": [ … ] } object, a bare array of tools, or even a single tool object. It also understands Anthropic input_schema and OpenAI parameters as aliases for MCP's inputSchema, so it works for function-calling tools too.
Frequently asked questions
How do I get my server's tools/list output?
Most MCP inspectors and client logs can dump the tools/list response, or you can call the server's tools/list method directly. Paste whatever JSON it returns.
Does it check whether a tool is safe?
No — this is a structural and schema review. To scan a server's tool descriptions for hidden or malicious instructions, use the MCP Security Scanner.
Why does it warn about a missing description?
The model uses each tool's description to decide when to call it and how to fill its arguments. A tool or parameter with no description is much harder for the model to use correctly.
Is my JSON uploaded?
No. Parsing and validation happen entirely in your browser.
Related searches
Related Developer tools
🔗 Embed this tool on your website — free
Copy this and paste it into your page's HTML. The tool runs in the visitor's browser, just like here. Change height to fit, or add the optional auto-resize snippet below. Add ?theme=dark to the URL for dark mode.
<iframe src="https://toolhq.dev/embed/mcp-tools-list-inspector/" title="MCP tools/list Inspector — ToolsHub" width="100%" height="520" style="border:1px solid #e5e7eb;border-radius:12px;max-width:680px" loading="lazy"></iframe>Optional: auto-resize the iframe height
Add this once on the same page so the iframe grows to fit the tool:
<script>
addEventListener("message", function (e) {
if (e.data && e.data.type === "toolshub:resize") {
document.querySelectorAll('iframe[src*="/embed/"]').forEach(function (f) {
if (f.contentWindow === e.source) f.style.height = e.data.height + "px";
});
}
});
</script>