Home / Token cost / Tlpt

The Tlpt MCP server costs 1,252 tokens before the first call.

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

QUICK ANSWER The Tlpt MCP server's tool definitions consume 1,252 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 17 tools · 1,252 tokens · 0.6% 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.6%
1M WINDOW 0.1%

Corpus context: Tlpt ranks #1980 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,252 tokens go.

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

ToolCategoryTokens% of server
register_exercise Write 169 13.5%
finding_register Write 130 10.4%
threat_profile Write 109 8.7%
tlpt_readiness Write 108 8.6%
phase_tracker Write 94 7.5%
auto_simulate Write 89 7.1%
remediation_plan Write 81 6.5%
team_assignment Write 79 6.3%
attack_chain Write 66 5.3%
mitre_map Write 59 4.7%
sync_to_ampel Write 52 4.2%
evidence_bundle Write 46 3.7%
generate_scenarios Write 41 3.3%
obligation_map Write 40 3.2%
test_calendar Read 36 2.9%
health_check Read 27 2.2%
ping Write 26 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 (74 tokens each).

Grant scopeDefinition costReduction
All 17 tools (no gateway) 1,252 tokens
3 granted tools ~221 tokens −82%
5 granted tools ~368 tokens −71%
10 granted tools ~736 tokens −41%

Tlpt token-cost questions.

How many tokens does the Tlpt MCP server use?+

Its 17 tool definitions total 1,252 tokens — 0.6% 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 Tlpt 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 Tlpt's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Tlpt 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 221 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 Tlpt tools. Counts refresh with every site build.

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

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