What problem does it solve?
MCP tool quality issues like poor discoverability, confusing descriptions, and schema errors are hard to fix without evidence. This Skill provides a disciplined campaign loop that measures the agent experience with an eval harness, picks the highest-impact problem from production data, makes one bounded fix, and ships it only if before/after scores improve.
Core Features & Use Cases
- Eval-driven measurement: Run probe mode (deterministic tool-presence and latency checks) and agent mode (LLM replay with task success and tool-selection scoring) against a seeded local stack.
- Evidence-based issue selection: Pull production signals with MCP analytics queries (tool stats, failures, descriptions, sample intents) and rank issues by reach times severity.
- Guardrailed shipping: Enforce a strict file allowlist, one issue per iteration, mandatory before/after benchmark evidence in every PR, and a campaign journal so later iterations can resume.
- Use Case: An agent notices agents frequently pass
sql instead of query to the execute-sql tool. It baselines the benchmark, clarifies the input description in tools.yaml, re-runs the harness, confirms task success improves from 19/27 to 22/27, and opens a draft PR with the eval evidence block.
Quick Start
Ask the agent to run an improve-my-MCP campaign against the local MCP stack and fix the highest-impact tool problem with eval evidence.