Don't auto-convert OpenAPI specs into 200 MCP tools — design from one user task
gethackteam · x · 2026-09-17
Auto-converting an OpenAPI spec into 200 MCP tools leaves too many API design decisions for the model to figure out, argues gethackteam. Instead, start with one concrete user task, expose only the operations needed to finish it, and add more tools only when you can show what's missing — a task-driven approach that meaningfully reduces the model's selection burden.
More from coding & agent
- Databricks rolled Astra out to all 3,500 engineers: beats Opus 5 on complex tasks, +60% coding spend — gdb · 2026-09-17
- Texio: fail-closed Markdown section edits for coding agents, open-sourced under MIT — yjthegnius · 2026-09-17
- Texio: fail-closed Markdown section edits for coding agents, open-sourced under MIT — yjthegnius · 2026-09-17
- Agent Dev Pattern: Store a 'Consent Record' Before Every Agent Run — blaizedsouza · 2026-09-17
- A practical prompt recipe for AI code review: solve it yourself first, then compare — dotey · 2026-09-17
- pi-crew brings non-blocking parallel subagent orchestration to the pi terminal AI — solyarisoftware · 2026-09-17