Agent Tool Spec Generator

Define a tool your AI agent can call. Generate a Markdown spec, JSON spec, input schema, and usage examples โ€” suitable for any agent framework, not just MCP.

Tool Details

Input Fields 0 defined

Output & Rules

// Fill in tool name and purpose to generateโ€ฆ
Generated in your browser. Nothing is uploaded.

How to define agent tools

๐ŸŽฏ

Name the action clearly

Use verb_noun: search_docs, create_ticket, get_user. The name is the primary signal for when the agent calls this tool.

๐Ÿ“

Write a precise description

Include what it does, what it returns, and when to call it. Vague descriptions cause wrong or missed tool calls.

๐Ÿšซ

Define when NOT to use it

This is often more important than when to use it. Prevents the agent from calling the tool inappropriately.

๐Ÿ›ก

Add safety rules

What should the tool never do? Only return authorised data, never expose secrets, max N results.

๐Ÿ”„

Document error handling

What should the agent do when the tool fails? Return empty array, retry, escalate?

๐Ÿ’ก

Include usage examples

Show the agent exactly what a call looks like. Examples are the most reliable way to improve tool selection accuracy.

Privacy: This tool runs in your browser. Nothing is uploaded or stored.

Frequently Asked Questions

What is an agent tool spec?
An agent tool spec is a complete definition of a tool an AI agent can call โ€” what it does, when to use it, what arguments it accepts, what it returns, and how it handles errors. Unlike an MCP tool definition which is specifically for MCP protocol, a tool spec is broader and can be used with any agent framework.
How is this different from the MCP Tool Definition Generator?
The MCP Tool Definition Generator targets the specific MCP protocol format (name, description, inputSchema). This Agent Tool Spec Generator produces a broader specification that includes when NOT to use the tool, output description, safety rules, error handling, and usage examples โ€” useful for any agent framework, not just MCP.
What is the JSON Spec output?
The JSON Spec is a machine-readable version of the full tool spec โ€” including name, description, when_to_use, when_not_to_use, input_schema, output, safety_rules, error_handling, and examples. You can store this in a tools registry or use it to auto-generate documentation.
What is the Input Schema output?
The Input Schema tab outputs just the JSON Schema-style inputSchema object. This is directly compatible with MCP tool definitions and other frameworks that accept JSON Schema for tool inputs.
Is my data uploaded anywhere?
No. This tool runs entirely in your browser. Nothing is sent to any server.