audit-mcp-tool-friction

Installation
SKILL.md

Audit MCP Tool Friction

Audit whether an agent that has chosen a tool can form a valid request, recover from a failure, and use the returned value. This is a public-contract audit, not a call-count target and not a test of model willingness to use a tool.

Set the boundary

Record the tool, revision, client, task or trace, and public inputs inspected. Keep these questions separate:

  • Adoption: whether the agent saw, discovered, or selected a tool.
  • Friction: whether the selected tool made its contract, valid input, error recovery, and result use clear enough to execute correctly.
  • Capability: whether an operation actually covers the requested work.

Do not call a successful Python fallback evidence that a tool contract is easy to use. Do not call a single malformed request a product defect without checking what the public contract exposed beforehand.

Installs
1
GitHub Stars
326
First Seen
Oct 26, 2026