Hiding a multi-agent system behind one MCP tool cuts token bloat and drift
anilkr84 · reddit · 2026-07-26
The author proposes hiding a multi-agent system behind a single MCP tool call, arguing that orchestration should happen server-side rather than in the client context.
They outline three generations of MCP server design:
- Box of tools: the client plans and threads state across thin stateless functions
- Tools + skillpack: the client still does all the work, only with better instructions
- Orchestration behind the boundary: one thick tool, such as askagent(goal), delegates to a server-side multi-agent system
The claimed benefits are flatter token costs, less goal drift, smaller client schemas, client portability, and a frozen contract that survives sub-agent swaps. The trade-offs are higher latency per call, less visibility into the chain, and the need to operate a real agent system in production.
The post ends by asking whether others have shipped “agent behind a tool” setups and where opacity became a problem.
Related event: Architecture Insight: Hiding Multi-Agent Orchestration in a Single MCP Tool(2 posts)→
More from coding & agent
- agents-best-practices: a provider-neutral Agent Skill for designing and auditing agentic harnesses — tom_doerr · 2026-09-11
- Cognition's SWE-2 uses a KKT duality argument in RL to shift the effort Pareto curve — YouJiacheng · 2026-09-11
- First-ever Three.js Conference lands in Paris, with a panel on AI-shortened design workflows — OdinLovis · 2026-09-11
- Data engineering, not agent frameworks, is the real bottleneck for enterprise AI agents — dhruv2038 · 2026-09-11
- RTK Terminal Compression Cuts Tokens but Leaves Your AI Coding Bill Unchanged — Bartaseth · 2026-09-11
- GPT-6 Astra beats Factorio with enemies in 44 in-game hours at ~$4,500 API cost — liminal_bardo · 2026-09-11