Home / Token cost / $THREE Token

The $THREE Token MCP server costs 557 tokens before the first call.

Every request your agent makes carries every tool definition this server exposes — context your code, documents and conversation can't use, mostly for tools the agent never calls. You don't need them all in the window, and you don't have to pay for them.

QUICK ANSWER The $THREE Token MCP server's 3 tool definitions consume 557 tokens — 0.3% of a 200k context window, and below the median MCP server (2,145 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

MEASURED FROM SCHEMAS tiktoken o200k_base · rank #4467 of 5,253 measured servers · refreshed every build Method →

What that costs 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.3%
1M WINDOW 0.1%

Corpus context: $THREE Token ranks #4467 of 5,253 measured MCP servers by definition cost. The median is 2,145 tokens, p90 is 11,440, and the heaviest (UnClick) is 147,411 — 74% of a 200k window on its own. New to this? See MCP token cost and context window in the glossary.

Where the 557 tokens go.

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

ToolCategoryTokens% of server
three_burn Destructive 335 60.1%
three_balance Read 111 19.9%
three_price Read 111 19.9%

Your agent uses a handful of these tools. It pays for all 3.

You don't need all 3 of those definitions in the window. PolicyLayer is an MCP gateway that sits in front of $THREE Token: only the tools you grant are exposed to the agent, the rest never load. A smaller window means a sharper agent — less noise when it picks a tool — and every request costs less:

At 3 tools, $THREE Token is already a small surface — the win here is policy control and audit rather than token savings.

The risk dividend: 1 of these 3 tools are critical-risk (destructive or financial) and cost 335 tokens (60% of the definition load). Block them — the recommended starter policy — and you reclaim that context before tuning anything else.

  1. Create a free account and register $THREE Token — nothing to install.
  2. Grant only the tools you use — ungranted definitions never enter the context window.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CUT $THREE TOKEN TOKEN COST →

Instant setup, no code required.

$THREE Token token-cost questions.

How many tokens does the $THREE Token MCP server use?+

Its 3 tool definitions total 557 tokens — 0.3% 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 $THREE Token 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 $THREE Token's token usage?+

Expose fewer tools. A PolicyLayer grant scopes $THREE Token to only the tools you allow — ungranted definitions are filtered out of the tool list, so they never enter the context window.

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 15-07-2026 from the PolicyLayer scan database over all 3 catalogued $THREE Token tools. Counts refresh with every site build.

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

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

Instant setup, no code required.

46,500+ MCP servers and 515,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.