MCP tool chains burn context on intermediate data; letting models write scripts wins on tokens
Future_AGI · reddit · 2026-08-21
A team shares a concrete comparison between wrapping APIs as MCP tools and letting the model write code. On a task that pulled records from one service, filtered them, and forwarded a subset to another, chained MCP tool calls meant a round trip per step, with most tokens spent on intermediate rows passing through the context window. Given the same two APIs and allowed to write a short script, the model finished in roughly one pass, with intermediate data never touching context.
Their rule of thumb: MCP earns its keep for discovery and auth (the parts you want standardized across servers), while for tight multi-step data work, code execution keeps winning on both calls and tokens.
More from coding & agent
- AI SDK author shares 25-min talk on his AI SDK factory for issue backlogs — lgrammel · 2026-08-21
- Recursive self-improvement is closer than it sounds, argues Philipp Schmid — _philschmid · 2026-08-21
- Building a searchable knowledge base from 14,000 tweets using Claude Code — eptwts · 2026-08-21
- Dev open-sources Tooldex: one dashboard to discover MCP servers across coding agents — sinfulfemale · 2026-08-21
- Minimax H3 ecosystem roundup: ComfyUI nodes, camera LoRAs, and RTX 3060 tests — optimisticalish · 2026-08-21
- Redis Launches Official Codex Plugin for Robust Development Workflows — npew · 2026-08-21