Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    mcp tool description engineer

    1

    Optimize MCP tool definitions and schemas to stop agents from calling the wrong tools or hallucinating parameters.

    $11

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    mcp tool description engineer

    mcp tool description engineer

    Example session with this skill installed

    My agent keeps using the 'get_log' tool for both system logs and application logs, but they require different parameters. How do I fix the tool definitions so it stops mixing them up?

    • Read your context and instructions
    • Compiled the mcp tool description
    1. Rename tools to 'get_system_audit_log' and 'get_app_runtime_log'.
    2. Add a WHEN clause: 'Use this only for OS-level events' vs 'Use for stack traces and app errors'.
    3. In inputSchema, change the generic 'id' parameter to 'service_name' with an enum of valid options.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    The problem

    Model selection accuracy degrades as you add more tools to an MCP server. Agents call the wrong functions, skip required parameters, or hallucinate argument values because your tool definitions are treated as documentation rather than steering signals.

    What it does

    • Audits existing tools/list payloads for naming collisions, ambiguous parameter schemas, and missing trigger conditions.
    • Rewrites tool names and descriptions to emphasize the decision boundary between similar capabilities.
    • Hardens inputSchema definitions using enums, format hints, and descriptive parameter names to prevent hallucinated values.
    • Architects namespacing and grouping strategies for servers exceeding 15 to 20 tools to maintain selection reliability.
    • Constructs a repeatable test battery to measure and verify tool-selection accuracy rates against realistic prompts.

    Frameworks & tools

    Model Context Protocol (MCP), JSON Schema, Anthropic tool-use specs.

    Why this beats prompting it yourself

    Writing tool definitions that "look right" to a human often fails in production because models respond to different linguistic cues. This skill applies verified patterns from primary MCP benchmarks to ensure the model picks the right tool every time, not just most of the time.

    Use cases

    • Fixing an agent that keeps calling search_users when it needs search_orders.
    • Refactoring a massive MCP server with 40+ tools that has become unreliable.
    • Preventing parameter hallucinations by tightening loose type: string definitions.
    • Validating tool selection accuracy before shipping a new MCP server to production.

    Known limitations

    This tool focuses on functional correctness and selection accuracy. It does not perform security audits for prompt injection or tool-poisoning vulnerabilities.

    Does not perform security audits for prompt injection or data exfiltration. Focused on functional selection accuracy, not safety or threat modeling.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Requires

    When Writing Or Auditing MCP
    Python

    Permissions

    No special permissions declared or detected

    Listed2 months ago
    Updated1 month ago

    What's inside

    Frequently Asked Questions

    This skill audits and rewrites your tool definitions to ensure models can clearly distinguish between similar functions, preventing common errors like parameter hallucinations or selecting the wrong tool in large servers.

    It is designed for any agent or platform using the Model Context Protocol (MCP) and JSON Schema, with specific optimization for Anthropic tool-use specifications.

    You receive a specialized engineering workflow that includes schema audit templates, naming convention guides, and a test battery to verify selection reliability across your MCP servers.

    This skill is particularly effective for large-scale deployments, providing namespacing and grouping strategies specifically designed to maintain reliability for servers with 20 to 40+ tools.

    While it hardens input schemas to prevent hallucinations and logic errors, it does not perform security audits or protect against intentional prompt injection attacks.

    Updates are released periodically to reflect the latest changes in the Model Context Protocol and evolving best practices for LLM tool-calling benchmarks.

    New in Agents & Orchestration