Home / Token cost / UK Legal Research

The UK Legal Research MCP server costs 11,350 tokens before the first call.

Connect UK Legal Research and its 34 tool definitions are loaded into the model's context on every request — 5.7% of a 200k window spent before your agent does anything.

QUICK ANSWER The UK Legal Research MCP server's tool definitions consume 11,350 tokens — 6.0× the median MCP server (1,905 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

MEASURED FROM SCHEMAS 34 tools · 11,350 tokens · 5.7% of 200k · 1.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 5.7%
1M WINDOW 1.1%

Corpus context: UK Legal Research ranks #146 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 11,350 tokens go.

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

ToolCategoryTokens% of server
parliament_search_hansard Read 913 8.0%
case_law_search Read 760 6.7%
parliament_policy_position_summary Read 678 6.0%
parliament_member_interests Read 595 5.2%
legislation_search Read 544 4.8%
citations_parse Execute 475 4.2%
legislation_get_section Read 468 4.1%
parliament_member_debates Read 468 4.1%
legislation_get_toc Read 457 4.0%
bills_search_bills Read 451 4.0%
parliament_get_debate_contributions Read 427 3.8%
votes_search_divisions Read 399 3.5%
committees_search_evidence Read 362 3.2%
parliament_lookup_by_column Read 357 3.1%
case_law_grep_judgment Read 356 3.1%
committees_search_committees Read 287 2.5%
parliament_search_petitions Read 286 2.5%
citations_resolve Write 286 2.5%
citations_network Read 273 2.4%
bills_get_bill Read 265 2.3%
parliament_find_member Read 248 2.2%
parliament_get_debate_divisions Read 240 2.1%
hmrc_check_mtd_status Read 214 1.9%
hmrc_get_vat_rate Read 212 1.9%
judgment_get_paragraph Read 191 1.7%
hmrc_search_guidance Read 190 1.7%
votes_get_division Read 190 1.7%
judgment_get_index Read 148 1.3%
judgment_get_header Read 147 1.3%
committees_get_committee Read 138 1.2%
get_prompt Read 115 1.0%
read_resource Read 96 0.8%
list_resources Read 68 0.6%
list_prompts Read 46 0.4%

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

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

Grant scopeDefinition costReduction
All 34 tools (no gateway) 11,350 tokens
3 granted tools ~1,001 tokens −91%
5 granted tools ~1,669 tokens −85%
10 granted tools ~3,338 tokens −71%

UK Legal Research token-cost questions.

How many tokens does the UK Legal Research MCP server use?+

Its 34 tool definitions total 11,350 tokens — 5.7% 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 UK Legal Research 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 UK Legal Research's token usage?+

Expose fewer tools. A PolicyLayer grant scopes UK Legal Research 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,001 tokens, a 91% 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 34 catalogued UK Legal Research tools. Counts refresh with every site build.

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

A PolicyLayer grant scopes UK Legal Research 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.