---
title: "toolset_too_large"
url: https://services.dev/docs/reference/check/toolset_too_large
---
# toolset_too_large

URL: https://services.dev/docs/reference/check/toolset_too_large

> The buyer's MCP toolset is over its token budget, so an agent's context fills with tools.

| Fix | Exit |
|---|---|
| Move Services to a brand of their own, or rows to the sandbox toolset: the order tools already fold into one. | 1 |

No failing file is captured. Past 12 Services, or sooner when one order tool per Service would cost more than 75% of the budget, a brand’s order tools fold into one, `order_job`, which names its Service in the arguments. So a brand reaches this gate only with well over a hundred Services. `check` prints the number it judges on every run, on its `mcp` line: the buyer’s tools, their tokens and the budget.

A brand of 13 Services, folded under one order tool, as `check` printed it:

```txt title="npx services.dev check"
mcp     13 buyer tools · 4,651 of 8,000 tokens · 9 more with ?toolset=sandbox
```

---

- Up: [check’s gates](https://services.dev/docs/reference/check.md)
- Previous: [agent_cannot_buy](https://services.dev/docs/reference/check/agent_cannot_buy.md)
- Next: [instructions_too_long](https://services.dev/docs/reference/check/instructions_too_long.md)