Designing MCP tools for bounded context
Bounded tool outputs keep the plan alive without sacrificing evidence. Here's how to design MCP tools that stay useful under a tight token budget.
Why bounded outputs matter
Unlimited tool responses eventually blow the window. Budgeted outputs force the system to prioritize the most relevant evidence for the current step, preserving space for reasoning.
Designing for code tasks
Each tool should target a specific code shape - symbols, references, related files, or architecture summaries. Structured outputs deliver high signal with minimal tokens and reduce redundant file pulls.
Budget-aware retrieval
Budgeted tools let you trade breadth for depth as the task evolves. Ask for a tight summary first, then expand only where needed to keep compaction at bay.