- Home
- Skills
- Agents & Orchestration
- Tool-Calling Failure Debugger
Works with the AI Agents you already use
Tool-Calling Failure Debugger
Diagnose tool-calling failures, schema mismatches, and unsafe agentic workflows with a structured audit framework.
$14.99
Tool-Calling Failure Debugger
Example session with this skill installed
My agent is failing to update user records. It keeps trying to call the 'get_user' tool instead of 'update_user', and when it does pick the right one, the 'user_id' is a string instead of an int.
- Read your context and instructions
- Compiled the tool-calling failure debugger
Root Cause: Description Ambiguity & Schema Mismatch.
Verdict: Material tool-calling failures.
Score: 62/100.
Findings
- High: 'update_user' description lacks 'when to use' constraints, causing 'get_user' to dominate selection.
- Medium: Schema expects integer ID; prompt lacks type-casting instruction.
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
Tool-calling workflows fail in production due to subtle schema drifts, ambiguous descriptions, or unsafe retry logic. Developers struggle to trace why an LLM selected the wrong tool, hallucinated arguments, or ignored approval gates during complex multi-step actions.
What it does
- Analyzes tool-call traces to pinpoint where discovery, selection, or argument construction diverged from intent.
- Audits JSON schemas and tool descriptions for ambiguities that trigger routing errors or validation failures.
- Evaluates safety controls including permission scoping, idempotency keys, and manual approval gating for destructive actions.
- Detects architectural risks like tool-output injection, infinite loops, and state loss in multi-turn sequences.
- Generates a remediation plan with a 100-point safety score and specific test cases for failure recovery.
Why this beats prompting it yourself
Standard prompts often miss edge cases like partial failure recovery or tool-output injection risks. This skill applies a structured 25-step audit workflow and a specialized failure catalog to ensure no part of the tool-execution lifecycle is overlooked.
Use cases
- Debugging why an agent repeatedly calls the same tool with invalid JSON arguments.
- Reviewing MCP tool routing and permissions before deploying to a production environment.
- Auditing side-effect safety for tools that handle payments, messaging, or data deletion.
- Designing robust retry and timeout logic for tools that interact with unstable third-party APIs.
Known limitations
This tool does not execute live API calls or modify production systems. It is a diagnostic and design-time auditor, not a runtime monitoring agent or automated testing suite.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.
Does not execute live tools or scripts. Requires manual provision of logs, traces, or schemas. Analyzes one coherent workflow at a time rather than entire distributed systems.
How to use
- 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
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
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 3 months ago
Permissions
No special permissions declared or detected