MCP Tool Schema Designer

Drafts a well-scoped MCP (Model Context Protocol) tool definition: name, description, input schema, and output shape.

Agentic AI and Multi-Agent Systemsintermediate8 minNo ratings yet

When to use this

Use when exposing a capability to an agent as an MCP tool and you want the schema to be unambiguous to a model, not just valid JSON Schema.

Prompt template

You are designing an MCP tool. Capability to expose: {{capability_description}}
Inputs it needs: {{inputs_description}}
What it returns: {{outputs_description}}

Produce:
1. A tool name (snake_case, verb-first) and a one-sentence description written for a model deciding whether to call it.
2. A JSON Schema for the input parameters, marking required fields and giving each a description a model can act on.
3. The output shape (fields and types), including how errors are represented.
4. One example call and one example response.
5. A note on what this tool must NOT be used for, if its name/description alone could be misread.

Customize

Capability to expose is required

Inputs it needs is required

What it returns is required

Preview

You are designing an MCP tool. Capability to expose: {{capability_description}} missing
Inputs it needs: {{inputs_description}} missing
What it returns: {{outputs_description}} missing

Produce:
1. A tool name (snake_case, verb-first) and a one-sentence description written for a model deciding whether to call it.
2. A JSON Schema for the input parameters, marking required fields and giving each a description a model can act on.
3. The output shape (fields and types), including how errors are represented.
4. One example call and one example response.
5. A note on what this tool must NOT be used for, if its name/description alone could be misread.

Usage instructions

Describe the capability in plain language first; let the prompt derive the schema rather than writing JSON Schema by hand and asking for a description to match it.

Example output

Tool name `get_order_shipping_status`, an input schema requiring `order_id: string`, an output shape with `status`, `estimated_delivery`, `tracking_url`, and an `error` field for not-found, plus a usage note clarifying it does not cancel or modify orders.

Limitations

Produces a design, not a working server implementation; you still need to wire it to your actual MCP server code.

Rate this prompt

Not yet rated