Home / Token cost / Buda

The Buda MCP server costs 3,436 tokens before the first call.

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

QUICK ANSWER The Buda MCP server's tool definitions consume 3,436 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 16 tools · 3,436 tokens · 1.7% of 200k · 0.3% 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 1.7%
1M WINDOW 0.3%

Corpus context: Buda ranks #1235 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 3,436 tokens go.

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

ToolCategoryTokens% of server
get_technical_indicators Read 349 10.2%
calculate_position_size Read 323 9.4%
get_price_history Read 301 8.8%
get_arbitrage_opportunities Read 290 8.4%
simulate_order Read 264 7.7%
get_real_quotation Read 257 7.5%
get_trades Read 214 6.2%
get_market_summary Read 193 5.6%
get_orderbook Read 173 5.0%
get_ticker Read 166 4.8%
get_spread Read 163 4.7%
compare_markets Read 159 4.6%
get_market_sentiment Read 158 4.6%
get_markets Read 145 4.2%
get_available_banks Read 142 4.1%
get_market_volume Read 139 4.0%

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

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 (215 tokens each).

Grant scopeDefinition costReduction
All 16 tools (no gateway) 3,436 tokens
3 granted tools ~644 tokens −81%
5 granted tools ~1,074 tokens −69%
10 granted tools ~2,148 tokens −38%

Buda token-cost questions.

How many tokens does the Buda MCP server use?+

Its 16 tool definitions total 3,436 tokens — 1.7% 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 Buda 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 Buda's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Buda 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 644 tokens, a 81% 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 16 catalogued Buda tools. Counts refresh with every site build.

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

A PolicyLayer grant scopes Buda 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.