Home / Token cost / GRID

The GRID MCP server costs 1,047 tokens before the first call.

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

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

MEASURED FROM SCHEMAS 16 tools · 1,047 tokens · 0.5% of 200k · 0.1% 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 0.5%
1M WINDOW 0.1%

Corpus context: GRID ranks #2148 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 1,047 tokens go.

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

ToolCategoryTokens% of server
grid_setup_business Write 169 16.1%
grid_inquire Execute 99 9.5%
grid_register Write 94 9.0%
grid_pay Financial 79 7.5%
grid_propose Read 71 6.8%
grid_rate Execute 67 6.4%
grid_search Read 64 6.1%
grid_my_deals Read 61 5.8%
grid_counter Write 61 5.8%
grid_send_message Write 56 5.3%
grid_accept_deal Read 51 4.9%
grid_get_agent Read 42 4.0%
grid_pending_approvals Read 37 3.5%
grid_deal_status Read 35 3.3%
grid_discover Read 34 3.2%
grid_health Read 27 2.6%

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

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

Grant scopeDefinition costReduction
All 16 tools (no gateway) 1,047 tokens
3 granted tools ~196 tokens −81%
5 granted tools ~327 tokens −69%
10 granted tools ~654 tokens −38%

GRID token-cost questions.

How many tokens does the GRID MCP server use?+

Its 16 tool definitions total 1,047 tokens — 0.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 GRID 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 GRID's token usage?+

Expose fewer tools. A PolicyLayer grant scopes GRID 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 196 tokens, a 81% 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 16 catalogued GRID tools. Counts refresh with every site build.

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

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