Dynamic tool discovery instead of loading every MCP schema upfront — worth the overhead?
Beginning-Fudge-5025 · reddit · 2026-11-14
The poster examines a common agent engineering pain: connecting multiple MCP servers loads descriptions and schemas for many tools the agent may never use, wasting context — especially on smaller windows or multi-domain agents. They explore dynamic tool discovery, where the agent searches for a capability and only loads the full tool definition on demand, citing Monid (a CLI/MCP tool catalogue they're affiliated with) as an example.
They ask practitioners: do you load schemas on demand, build a separate tool router, or keep a fixed toolset — and does dynamic discovery actually cut context usage in practice, or does the discovery step add its own overhead?
More from coding & agent
- Agent skills are everywhere — but they're just markdown files installed via npx — kylegawley · 2026-11-14
- Put your codebase on intermittent fasting: schedule what your agent may touch — vincent_koc · 2026-11-14
- HeyGen open-sources Hyperframes: HTML/CSS animations in, deterministic MP4 out for coding agents — victor_explore · 2026-11-14
- I asked my agent to purge 1M lines of code — tests now make up 60% of 13M — vincent_koc · 2026-11-14
- Claude Code client UI is now customizable, dev builds a personal workbench sidebar — xiaohu · 2026-11-14
- HFS survey: two-thirds of AI leaders say tribal knowledge is undocumented; firms hit a wall at ~5 agents — ombre-ai · 2026-11-14