Home / Token cost / Simplefunctions

The Simplefunctions MCP server costs 15,021 tokens before the first call.

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

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

MEASURED FROM SCHEMAS 108 tools · 15,021 tokens · 7.5% of 200k · 1.5% 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 7.5%
1M WINDOW 1.5%

Corpus context: Simplefunctions ranks #93 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 15,021 tokens go.

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

ToolCategoryTokens% of server
screen_markets Read 605 4.0%
monitor_the_situation Read 551 3.7%
create_intent Write 447 3.0%
create_strategy Write 375 2.5%
fork_thesis Read 296 2.0%
configure_heartbeat Write 295 2.0%
update_nodes Write 290 1.9%
query_databento Read 288 1.9%
update_strategy Write 257 1.7%
create_skill Write 256 1.7%
inspect_ticker Read 245 1.6%
add_position Write 232 1.5%
search_x Read 198 1.3%
post_to_forum Write 196 1.3%
update_position Write 196 1.3%
portfolio_attribution_grouped Read 186 1.2%
enrich_content Read 183 1.2%
get_regime_scan Read 182 1.2%
create_thesis Write 180 1.2%
portfolio_positions_list Read 177 1.2%
what_if Read 172 1.1%
update_thesis Write 170 1.1%
get_context Read 163 1.1%
get_trade_ideas Read 160 1.1%
get_markets Read 158 1.1%
read_forum Read 157 1.0%
get_world_state Read 153 1.0%
inject_signal Write 153 1.0%
query_econ Read 152 1.0%
get_forecast Read 151 1.0%
list_intents Read 147 1.0%
x_volume Read 147 1.0%
portfolio_attribution_daily Read 146 1.0%
get_edges Read 144 1.0%
portfolio_ledger_list Read 143 1.0%
screen_by_tickers Read 142 0.9%
x_account Read 141 0.9%
portfolio_activity_list Read 139 0.9%
scan_markets Read 136 0.9%
portfolio_fills_list Read 134 0.9%
get_market_diff Read 132 0.9%
publish_skill Write 125 0.8%
get_world_delta Read 123 0.8%
query_gov Read 122 0.8%
browse_public_skills Read 121 0.8%
get_market_microstructure_history Read 121 0.8%
augment_tree Read 120 0.8%
get_yield_curves Read 119 0.8%
list_strategies Read 119 0.8%
x_news Read 118 0.8%
query Read 117 0.8%
get_contagion Read 113 0.8%
get_newmarkets Read 113 0.8%
get_changes_delta Read 112 0.7%
tts Read 112 0.7%
get_heartbeat_status Read 110 0.7%
get_changes Read 109 0.7%
get_evaluation_history Read 109 0.7%
trigger_evaluation Execute 108 0.7%
get_calibration Read 108 0.7%
get_thesis_context Read 108 0.7%
list_legislation Read 108 0.7%
close_position Write 108 0.7%
get_market_detail Read 107 0.7%
get_feed Read 106 0.7%
get_economic_anchors Read 105 0.7%
run_skill Execute 104 0.7%
get_milestones Read 104 0.7%
list_congress_members Read 103 0.7%
get_calendar Read 102 0.7%
get_orders Read 102 0.7%
fork_skill Read 101 0.7%
get_agent_guide Read 100 0.7%
get_positions Read 99 0.7%
cancel_intent Destructive 96 0.6%
batch_markets Read 93 0.6%
get_heartbeat_config Read 93 0.6%
get_settlements Read 92 0.6%
get_answer Read 91 0.6%
get_yield_curve Read 90 0.6%
get_fills Read 89 0.6%
subscribe_forum Read 89 0.6%
stt Read 88 0.6%
get_briefing Read 86 0.6%
list_opinions Read 85 0.6%
get_index_history Read 83 0.6%
get_market_index Read 79 0.5%
legislation Read 78 0.5%
list_skills Read 78 0.5%
get_legislation Read 77 0.5%
explore_public Read 76 0.5%
list_forum_channels Read 76 0.5%
get_balance Read 75 0.5%
list_technicals Read 74 0.5%
list_theses Read 74 0.5%
explore_theses Read 71 0.5%
get_market_history Read 71 0.5%
portfolio_risk_get Read 71 0.5%
get_skills Read 70 0.5%
list_glossary Read 70 0.5%
site_search Read 65 0.4%
get_congress_member Read 64 0.4%
get_glossary_term Read 64 0.4%
get_highlights Read 62 0.4%
get_technical Read 60 0.4%
get_opinion Read 59 0.4%
get_public_skill Read 59 0.4%
get_schedule Read 42 0.3%

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

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

Grant scopeDefinition costReduction
All 108 tools (no gateway) 15,021 tokens
3 granted tools ~417 tokens −97%
5 granted tools ~695 tokens −95%
10 granted tools ~1,391 tokens −91%

Simplefunctions token-cost questions.

How many tokens does the Simplefunctions MCP server use?+

Its 108 tool definitions total 15,021 tokens — 7.5% 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 Simplefunctions 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 Simplefunctions's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Simplefunctions 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 417 tokens, a 97% 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 108 catalogued Simplefunctions tools. Counts refresh with every site build.

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

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