Home / Token cost / Pensiata - Bulgarian Pension Fund Analytics

The Pensiata - Bulgarian Pension Fund Analytics MCP server costs 4,076 tokens before the first call.

Connect Pensiata - Bulgarian Pension Fund Analytics and its 26 tool definitions are loaded into the model's context on every request — 2.0% of a 200k window spent before your agent does anything.

QUICK ANSWER The Pensiata - Bulgarian Pension Fund Analytics MCP server's tool definitions consume 4,076 tokens — 2.1× the median MCP server (1,905 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

MEASURED FROM SCHEMAS 26 tools · 4,076 tokens · 2.0% of 200k · 0.4% 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 2.0%
1M WINDOW 0.4%

Corpus context: Pensiata - Bulgarian Pension Fund Analytics ranks #1137 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 4,076 tokens go.

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

ToolCategoryTokens% of server
compute_metric Read 314 7.7%
rank Read 283 6.9%
get_bulgarian_pension_fund_metric Read 277 6.8%
rank_bulgarian_pension_funds_by_metric Read 260 6.4%
rank_bulgarian_pension_benchmarks_by_metric Read 258 6.3%
rank_benchmarks Read 234 5.7%
get_nav_series Read 223 5.5%
read_holdings_report Read 204 5.0%
simulate_saver_outcome Read 185 4.5%
get_bulgarian_pension_fund_nav_series Read 182 4.5%
list_holdings_reports Read 178 4.4%
get_holdings_reports_index Read 165 4.0%
get_benchmark_series Read 145 3.6%
simulate_bulgarian_pension_saver_outcome Read 144 3.5%
list_funds Read 138 3.4%
search_pension_law Read 130 3.2%
get_bulgarian_pension_benchmark_series Read 129 3.2%
list_managers Read 118 2.9%
get_bulgarian_pension_funds Read 97 2.4%
get_pension_legal_framework Read 90 2.2%
get_bulgarian_pension_fund_managers Read 80 2.0%
list_benchmarks Read 80 2.0%
get_bulgarian_pension_metrics_catalog Read 47 1.2%
get_bulgarian_pension_benchmarks Read 46 1.1%
list_metrics Read 35 0.9%
cache_stats Read 34 0.8%

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

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

Grant scopeDefinition costReduction
All 26 tools (no gateway) 4,076 tokens
3 granted tools ~470 tokens −88%
5 granted tools ~784 tokens −81%
10 granted tools ~1,568 tokens −62%

Pensiata - Bulgarian Pension Fund Analytics token-cost questions.

How many tokens does the Pensiata - Bulgarian Pension Fund Analytics MCP server use?+

Its 26 tool definitions total 4,076 tokens — 2.0% 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 Pensiata - Bulgarian Pension Fund Analytics 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 Pensiata - Bulgarian Pension Fund Analytics's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Pensiata - Bulgarian Pension Fund Analytics 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 470 tokens, a 88% 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 26 catalogued Pensiata - Bulgarian Pension Fund Analytics tools. Counts refresh with every site build.

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

A PolicyLayer grant scopes Pensiata - Bulgarian Pension Fund Analytics 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.