Home / Token cost / TaskMan of London

The TaskMan of London MCP server costs 2,955 tokens before the first call.

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

QUICK ANSWER The TaskMan of London MCP server's tool definitions consume 2,955 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 20 tools · 2,955 tokens · 1.5% 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.5%
1M WINDOW 0.3%

Corpus context: TaskMan of London ranks #1312 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,955 tokens go.

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

ToolCategoryTokens% of server
create_booking_request Write 362 12.3%
create_customer_booking Write 289 9.8%
get_quote_estimate Read 216 7.3%
start_booking_payment Execute 212 7.2%
match_providers Read 201 6.8%
get_customer_availability Read 180 6.1%
get_booking_status Read 170 5.8%
check_availability Read 164 5.5%
start_customer_verification Execute 125 4.2%
find_services Read 114 3.9%
get_booking_payment_status Read 109 3.7%
tag_contact Write 109 3.7%
check_service_area Read 107 3.6%
verify_customer_otp Read 107 3.6%
update_contact_note Write 97 3.3%
start_trusted_phone_session Execute 90 3.0%
verify_magic_link_token Read 77 2.6%
get_customer_profile Read 76 2.6%
list_customer_addresses Read 75 2.5%
list_service_types Read 75 2.5%

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

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

Grant scopeDefinition costReduction
All 20 tools (no gateway) 2,955 tokens
3 granted tools ~443 tokens −85%
5 granted tools ~739 tokens −75%
10 granted tools ~1,478 tokens −50%

TaskMan of London token-cost questions.

How many tokens does the TaskMan of London MCP server use?+

Its 20 tool definitions total 2,955 tokens — 1.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 TaskMan of London 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 TaskMan of London's token usage?+

Expose fewer tools. A PolicyLayer grant scopes TaskMan of London 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 443 tokens, a 85% 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 20 catalogued TaskMan of London tools. Counts refresh with every site build.

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

A PolicyLayer grant scopes TaskMan of London 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.