Home / Token cost / Vaquill

The Vaquill MCP server costs 2,773 tokens before the first call.

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

QUICK ANSWER The Vaquill MCP server's tool definitions consume 2,773 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 15 tools · 2,773 tokens · 1.4% 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.4%
1M WINDOW 0.3%

Corpus context: Vaquill ranks #1341 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,773 tokens go.

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

ToolCategoryTokens% of server
list_legislation Read 291 10.5%
ask_legal_question Read 274 9.9%
search_legal_cases Read 268 9.7%
search_legislation Read 252 9.1%
search_cases_by_citation Read 237 8.5%
search_us_statutes Read 222 8.0%
quick_search Read 215 7.8%
get_citation_network Read 188 6.8%
get_amendments Read 168 6.1%
resolve_citation Write 140 5.0%
get_us_statute_section Read 122 4.4%
lookup_case Read 122 4.4%
get_us_statute_section_text Read 108 3.9%
get_act_text Read 99 3.6%
get_pricing Read 67 2.4%

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

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

Grant scopeDefinition costReduction
All 15 tools (no gateway) 2,773 tokens
3 granted tools ~555 tokens −80%
5 granted tools ~924 tokens −67%
10 granted tools ~1,849 tokens −33%

Vaquill token-cost questions.

How many tokens does the Vaquill MCP server use?+

Its 15 tool definitions total 2,773 tokens — 1.4% 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 Vaquill 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 Vaquill's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Vaquill 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 555 tokens, a 80% 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 15 catalogued Vaquill tools. Counts refresh with every site build.

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

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