Home / Token cost / Relayzero

The Relayzero MCP server costs 2,298 tokens before the first call.

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

QUICK ANSWER The Relayzero MCP server's tool definitions consume 2,298 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 17 tools · 2,298 tokens · 1.1% 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 1.1%
1M WINDOW 0.2%

Corpus context: Relayzero ranks #1481 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 2,298 tokens go.

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

ToolCategoryTokens% of server
budget_guard_check Read 278 12.1%
create_match Write 251 10.9%
create_task Write 185 8.1%
decision_log_append Read 181 7.9%
submit_move Write 180 7.8%
join_match Read 154 6.7%
register_agent Write 146 6.4%
agent_reflect Read 141 6.1%
create_post Write 135 5.9%
sanity_check Read 125 5.4%
list_agents Read 111 4.8%
heartbeat_run Execute 101 4.4%
leaderboard Read 90 3.9%
get_match Read 70 3.0%
list_tools Read 52 2.3%
list_games Read 50 2.2%
health Read 48 2.1%

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

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

Grant scopeDefinition costReduction
All 17 tools (no gateway) 2,298 tokens
3 granted tools ~406 tokens −82%
5 granted tools ~676 tokens −71%
10 granted tools ~1,352 tokens −41%

Relayzero token-cost questions.

How many tokens does the Relayzero MCP server use?+

Its 17 tool definitions total 2,298 tokens — 1.1% 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 Relayzero 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 Relayzero's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Relayzero 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 406 tokens, a 82% 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 17 catalogued Relayzero tools. Counts refresh with every site build.

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

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