Home / Token cost / Sidearm

The Sidearm MCP server costs 2,756 tokens before the first call.

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

QUICK ANSWER The Sidearm MCP server's tool definitions consume 2,756 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 19 tools · 2,756 tokens · 1.4% 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.4%
1M WINDOW 0.3%

Corpus context: Sidearm ranks #1345 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,756 tokens go.

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

ToolCategoryTokens% of server
run_algorithm Execute 307 11.1%
protect_media Read 268 9.7%
search_media Read 216 7.8%
detect_membership Read 189 6.9%
register_media Write 186 6.7%
get_billing Read 184 6.7%
detect_fingerprint Read 180 6.5%
detect_ai Read 174 6.3%
list_algorithms Read 144 5.2%
navigate_ui Execute 132 4.8%
search_docs Read 122 4.4%
get_provenance Read 100 3.6%
list_media Read 99 3.6%
list_searches Read 89 3.2%
update_media Write 88 3.2%
check_job Read 79 2.9%
get_rights Read 78 2.8%
delete_media Destructive 62 2.2%
get_media Read 59 2.1%

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

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

Grant scopeDefinition costReduction
All 19 tools (no gateway) 2,756 tokens
3 granted tools ~435 tokens −84%
5 granted tools ~725 tokens −74%
10 granted tools ~1,451 tokens −47%

Sidearm token-cost questions.

How many tokens does the Sidearm MCP server use?+

Its 19 tool definitions total 2,756 tokens — 1.4% 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 Sidearm 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 Sidearm's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Sidearm 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 435 tokens, a 84% 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 19 catalogued Sidearm tools. Counts refresh with every site build.

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

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