Home / Token cost / DiscreteRate

The DiscreteRate MCP server costs 1,631 tokens before the first call.

Connect DiscreteRate and its 13 tool definitions are loaded into the model's context on every request — 0.8% of a 200k window spent before your agent does anything.

QUICK ANSWER The DiscreteRate MCP server's tool definitions consume 1,631 tokens — around the median MCP server (1,905 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

MEASURED FROM SCHEMAS 13 tools · 1,631 tokens · 0.8% of 200k · 0.2% of 1M Method →

What that buys before your agent starts working.

Tool definitions are overhead: they occupy context on every request and compete with your code, documents and conversation history for the same window.

200K WINDOW 0.8%
1M WINDOW 0.2%

Corpus context: DiscreteRate ranks #1744 of 3,213 measured MCP servers by definition cost. The median is 1,905 tokens, p90 is 7,952, and the heaviest (Fusionauth) is 183,337 — 92% of a 200k window on its own.

Where the 1,631 tokens go.

Each row is one tool definition as a tools/list entry — name, description and input schema — counted with o200k_base. Average: 125 tokens per tool.

ToolCategoryTokens% of server
run_valdez_tanker Execute 162 9.9%
run_tissue_line Execute 157 9.6%
run_sku_capacity Execute 147 9.0%
run_fast_slow_drain Execute 146 9.0%
run_chocolate_processing Execute 139 8.5%
run_hamburger_duo Execute 135 8.3%
describe_demo Read 135 8.3%
run_vegetable_plant Execute 129 7.9%
explain_discrete_rate_simulation Execute 111 6.8%
explain_des_vs_drs_event_complexity Write 107 6.6%
explain_paradigm_integration Execute 96 5.9%
list_drs_demos Read 87 5.3%
explain_three_primitives Write 80 4.9%

Most agents use a handful of these tools. They pay for all 13.

A PolicyLayer grant exposes only the tools you allow — ungranted definitions are filtered out of the tool list, so they never enter the context window. Estimates below assume typical-weight tools (125 tokens each).

Grant scopeDefinition costReduction
All 13 tools (no gateway) 1,631 tokens
3 granted tools ~376 tokens −77%
5 granted tools ~627 tokens −62%
10 granted tools ~1,255 tokens −23%

DiscreteRate token-cost questions.

How many tokens does the DiscreteRate MCP server use?+

Its 13 tool definitions total 1,631 tokens — 0.8% of a 200k context window — measured with tiktoken o200k_base over the serialised tools/list payload. Exact counts vary slightly by client and model.

Why does DiscreteRate consume tokens before I send a message?+

MCP clients load every connected server's tool definitions — name, description, and input schema — into the model's context so it knows what it can call. That payload is charged against your context window on every request, whether or not a tool is used.

How do I reduce DiscreteRate's token usage?+

Expose fewer tools. A PolicyLayer grant scopes DiscreteRate to only the tools you allow — ungranted definitions are filtered out of the tool list, so they never enter the context window. A grant of 3 typical tools costs roughly 376 tokens, a 77% reduction.

Does deferred tool loading fix this?+

Partially, in some clients. Claude Code defers MCP tool schemas behind a tool-search step by default, and VS Code has experimental grouping — but you still pay tokens per search and reload, and Cursor, Windsurf and Gemini CLI load definitions upfront. Reducing the exposed tool set cuts the cost in every client.

How these numbers were measured.

01
Serialisation

Each tool is serialised as a tools/list entry — name, description, input schema — from the schemas in the PolicyLayer scan database. Clients differ slightly in framing, so treat counts as close estimates.

02
Tokeniser

tiktoken o200k_base (GPT-4o/o-series). Anthropic's current tokeniser isn't published, so Claude's exact counts will differ; for English text and JSON schemas the totals are close enough to treat these as estimates.

03
Deferred loading

Some clients now defer schema loading (Claude Code's tool search; VS Code experimental grouping). You still pay per search and reload — and Cursor, Windsurf and Gemini CLI load everything upfront.

Computed 07-06-2026 from the PolicyLayer scan database over all 13 catalogued DiscreteRate tools. Counts refresh with every site build.

Expose only the tools you use — the rest never enter your context.

A PolicyLayer grant scopes DiscreteRate to the tools you actually allow. Ungranted definitions never load, and every call that does run is checked against policy first.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.