MCP lesson learned: collapse CRUD endpoints into fewer tools with enum params, not 20 granular ones
Relevant-Potential17 · reddit · 2026-09-19
After months of building MCP servers, the author's key lesson: don't mirror your REST API by exposing every CRUD endpoint as a separate tool.
- Past 15–20 granular tools, schemas clutter the system prompt, the model gets indecisive, hallucinates tool calls or picks the wrong one, and latency rises;
- Better: collapse into broader actions with enum params, e.g. manageuser(action="search"|"update", ...) or queryuser(filterby="id"|"email", value);
- Treat tool description fields as prompt engineering, not swagger docs — explicitly telling the model when NOT to call a tool cut bad invocations in half.
More from coding & agent
- Power user burns 1bn tokens a day at 98.65% cache hits, weighing GLM-5.3 vs DeepSeek after Claude Code weekly limits — julianharris · 2026-09-19
- Two MCP orchestration patterns: Jev as LLM tool orchestrator vs LLM as a tool — blaizedsouza · 2026-09-19
- Jev controls Ableton Live by voice, ~40x faster than LLM computer use — jordiponsdotme · 2026-09-19
- Dev wires up a vLLM reproduction in minutes with Codex, runs it on DGX Spark — remilouf · 2026-09-19
- Dev builds Vercel-like tool to turn any project into a hosted MCP server with one prompt — Corridl · 2026-09-19
- Querit launches coding-focused search built for code agents and IDEs — SucceededMind · 2026-09-19