Strategies for Loading Agent Tool Schemas
mattjcoles · reddit · 2026-07-17
The author explores loading strategies for MCP tool schemas within acme-mcp:
- Exposing a single generic querytool keeps the tool list concise, but hides parameter constraints and result shapes for different datasets from the model.
- Splitting them into multiple typed tools helps the model pick the right one, but a bloated catalog starts eating up context.
- Their current approach: having clients load detailed tool definitions progressively / on-demand, rather than dumping the entire catalog into the prompt upfront.
The post concludes by asking: at what scale should one switch from "explicitly exposing" tools to "progressive discovery"?
Related event: Balancing Precision and Context in MCP Data Tool Design(3 posts)→
More from coding & agent
- Coding agents are heading toward an AI-writes, AI-reviews, human-approves workflow — aftahi_ai · 2026-07-22
- oMLX 0.5.2 adds Mac menu-bar stats, low-bit decode kernels, and faster downloads — awnihannun · 2026-07-22
- GitHub review bot hits its PR limit and forces a 39-minute cooldown — DanielLockyer · 2026-07-22
- Max reasoning effort appears to be mobile-only in Codex Remote, not desktop — GabGarrett · 2026-07-22
- A Reddit demo argues online stores should expose carts and pricing through MCP — gelembjuk · 2026-07-22
- Open-source AI SDK provider routes Vercel apps through a local Codex subscription — lgrammel · 2026-07-22