# Tool bundling

**Source:** https://promtable.com/glossary/tool-bundling

> Tool bundling groups related tools behind a single high-level interface — so the agent calls one tool that does the right thing internally rather than choosing between many narrow tools.

---
Tool bundling groups related tools behind a single high-level interface — so the agent calls one tool that does the right thing internally rather than choosing between many narrow tools.

When agents have too many narrow tools (get_user, get_user_email, get_user_phone, get_user_address) they mis-route. Tool bundling exposes a single high-level tool (get_user_info with an args schema specifying which fields to return) that handles the dispatch internally. Empirically reduces mis-routing rates and simplifies the agent's surface area without losing capability. Best practice in 2026 is to bundle tools by user-facing intent rather than by underlying API endpoint, even if it means writing more glue code on the server side.

## When to use

- Agents with many narrow tools that overlap in intent.
- Production agents where mis-routing is materially degrading quality.

## Common mistakes

- Bundling too aggressively — the bundled tool's args schema becomes unwieldy.
- Not documenting the dispatch logic — debugging tool decisions becomes hard.

## Related terms

- [tool-use](https://promtable.com/glossary/tool-use)
- [tool-router](https://promtable.com/glossary/tool-router)
- [tool-shadowing](https://promtable.com/glossary/tool-shadowing)
- [function-calling](https://promtable.com/glossary/function-calling)

*Last updated: 2026-06-01*
---

Original page: https://promtable.com/glossary/tool-bundling
Maintained by Promtable (https://promtable.com). Content: CC BY 4.0. Cite as "Promtable — https://promtable.com/glossary/tool-bundling".
Contact: info@vibecodingturkey.com.