Home / Token cost / Cls

The Cls MCP server costs 8,577 tokens before the first call.

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

QUICK ANSWER The Cls MCP server's tool definitions consume 8,577 tokens — 4.5× 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 · 8,577 tokens · 4.3% of 200k · 0.9% 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 4.3%
1M WINDOW 0.9%

Corpus context: Cls ranks #217 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 8,577 tokens go.

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

ToolCategoryTokens% of server
GetAlarmLog Read 1,172 13.7%
SearchLog Read 1,063 12.4%
DescribeLogContext Read 592 6.9%
DescribeLogHistogram Read 579 6.8%
DescribeAlertRecordHistory Read 577 6.7%
QueryRangeMetric Read 564 6.6%
TextToSearchLogQuery Read 478 5.6%
DescribeAlarmShields Read 448 5.2%
QueryMetric Read 400 4.7%
DescribeWebCallbacks Read 318 3.7%
DescribeAlarms Read 317 3.7%
DescribeAlarmNotices Read 309 3.6%
DescribeNoticeContents Read 304 3.5%
GetAlarmDetail Read 296 3.5%
ConvertTimeStringToTimestamp Write 294 3.4%
DescribeIndex Read 263 3.1%
GetTopicInfoByName Read 241 2.8%
ConvertTimestampToTimeString Write 224 2.6%
GetRegionCodeByName Read 138 1.6%

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

Grant scopeDefinition costReduction
All 19 tools (no gateway) 8,577 tokens
3 granted tools ~1,354 tokens −84%
5 granted tools ~2,257 tokens −74%
10 granted tools ~4,514 tokens −47%

Cls token-cost questions.

How many tokens does the Cls MCP server use?+

Its 19 tool definitions total 8,577 tokens — 4.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 Cls 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 Cls's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Cls 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 1,354 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 Cls tools. Counts refresh with every site build.

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

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