MCP solves tool transport, not tool selection: why coding agents still prefer grep
Wise_Reflection_8340 · reddit · 2026-09-22
While integrating a structural code engine with several coding agents, the author found that exposing useful tools via MCP doesn't mean agents will use them. Their MCP server offers entity search, callers, dependencies, impact analysis, and bounded context, yet agents still default to grep and file reads. Suspected causes: stronger model priors for Unix tools, context overhead of MCP descriptions, multi-call latency, uncertainty about index coverage, and difficulty judging when structural queries win. They're experimenting with compound transactions — resolve → contextualize → edit → verify → receipt — where the receipt logs repo revision, changed entities, validation, and fallbacks. Open question: should MCP servers expose many precise tools, fewer compound operations, or both with a routing layer? Open-sourced as Ataraxy-Labs/sem.
More from coding & agent
- User automates entire video clipping workflow with Nous Research's Hermes agent — Teknium · 2026-11-12
- As models improve, writing good evals gets harder and more important — amankhan · 2026-11-12
- Prime agent ships with day-one multi-agent communication, runs in Minecraft unmodified — sarahcat21 · 2026-11-12
- Autonomous agent edits just 1,024 weights to lift Qwen3.5 0.8B from 7.4% to 37.4% on MATH-500 — VictorSanh · 2026-11-12
- Omarchy 4.6 lets you share local AI models across your tailnet, says DHH — alexcovo_eth · 2026-11-12
- Coding harnesses hand shell access to inference providers — 4-step gateway mitigation — shensi · 2026-11-12