MCP context budget

MCP Context Budget

A context budget turns tool catalog size into a number that platform teams can manage before latency, cost, or task failure becomes visible in production.

Open scanner preview

Operating steps

  1. Collect the server-card and tools/list output.
  2. Break the payload into tool name, description, input schema, enum, and example buckets.
  3. Estimate token load under the target model and context window.
  4. Set a threshold for eager loading, lazy loading, and removal.

Common risks

  • Token estimates vary by tokenizer and model family.
  • Tiny tools can still be expensive when schemas repeat deeply nested objects.
  • Budget reports should be updated whenever the server-card changes.