Context tool
Estimate how much MCP context rides along with every request.
MCP servers can contribute tool definitions and instructions to agent context. Enter the server count and a measured or assumed schema size to estimate standing context exposure.
Estimated standing context
4,800 tokens
Loaded before task-specific repository or prompt context when all selected tool schemas are present.
Daily context exposure
480,000 tokens
A repetition estimate, not a billing claim. Caching and deferred tool loading can materially change provider cost.
Use measured schema/context values when available. The default 1,200-token assumption is only a scenario input and is not presented as a vendor benchmark.
Interpret the number carefully
This is a context-exposure calculator, not a provider invoice calculator. Some agent harnesses load tools lazily and some providers discount cached input. Use an actual context export or measured schema size whenever possible, then use the free Agent Config Audit to inspect the rest of your always-on instruction footprint.
Run the Agent Config Audit →From estimate to policy
Knowing the cost is step one. Deciding the rules is step two.
This estimates what your tool schemas cost in standing context. A Cheat Code is where you write down which tools an agent may actually call, what needs confirmation first, and what it must never do unattended.