MCP tool schema inspector: diff your tools/list against the Sella reference
Paste the tools/list JSON-RPC response from your MCP server. The inspector compares it against Sella’s reference tool contracts and surfaces missing tools, schema drift, and empty descriptions. Runs entirely in your browser.
Sella reference tools
- sella_auth_start required: email
- sella_auth_complete required: email, otp_code
- sella_setup_claim required: code
- list_datasets required: none
- search_datasets required: none
- try_dataset required: dataset_id
- get_dataset required: dataset_id
- cradle_breed_agent required: none
- merge_models required: config_yaml
- list_market_apis required: none
- search_open_models required: query
- search_catalog required: none
- describe_catalog required: none
- get_listing required: listing_id
- recommend required: none
- compare required: listing_ids
- submit_feedback required: listing_id, type
- get_activity required: none
- get_job required: job_id
- policy_get required: none
- policy_set required: none
- policy_check required: none
- budget_status required: none
- purchase_preview required: listing_id
- explain_decision required: receipt_id
- get_approval required: none
Why MCP schema correctness matters
Agents pick tools based on the description and shape of inputSchema. A mis-typed required field or a vague description silently breaks tool-calling. The agent tries the wrong arguments, gets a 4xx, and either retries blindly or gives up. Validating your server against a known-good reference catches these issues before agents ever see them.
The Sella reference contract lives at /playground where you can call the live tools/list endpoint and try each tool against the marketplace.
FAQ
- What does this tool check for?
- Three things: (1) tools missing from your server that Sella expects, (2) schema drift on matched tools: missing/extra properties, wrong required fields, empty descriptions, (3) extra vendor-specific tools that Sella doesn’t reference.
- What payload format does it accept?
- Paste the raw JSON-RPC response body from a tools/list request: either the full envelope ({"jsonrpc":"2.0","result":{"tools":[...]}}, just the inner result, a bare {"tools":[...]} object, or a bare array of tool objects.
- Does this share my payload anywhere?
- No. The inspector runs entirely in your browser. No payload data is sent to Sella servers.
Sella, the economy for AI agents
Discover, preview, and pay for machine-payable datasets, evals, and APIs on the Sella marketplace. Or publish your own.