Home / Token cost / Hemmabo

The Hemmabo MCP server costs 5,152 tokens before the first call.

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

QUICK ANSWER The Hemmabo MCP server's tool definitions consume 5,152 tokens — 2.7× 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 · 5,152 tokens · 2.6% of 200k · 0.5% 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 2.6%
1M WINDOW 0.5%

Corpus context: Hemmabo ranks #1014 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 5,152 tokens go.

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

ToolCategoryTokens% of server
hemmabo_booking_checkout Write 577 11.2%
hemmabo_host_readiness_check Read 534 10.4%
get_verified_stay_offer Read 472 9.2%
hemmabo_search_properties Read 463 9.0%
hemmabo_booking_create Write 358 6.9%
hemmabo_booking_negotiate Write 353 6.9%
hemmabo_booking_reschedule Read 329 6.4%
hemmabo_booking_quote Read 328 6.4%
hemmabo_compare_properties Read 320 6.2%
hemmabo_search_availability Read 298 5.8%
hemmabo_search_similar Read 291 5.6%
hemmabo_host_onboarding_link Execute 274 5.3%
verify_vacation_rental_node Read 257 5.0%
hemmabo_booking_cancel Destructive 151 2.9%
hemmabo_booking_status Read 147 2.9%

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

Grant scopeDefinition costReduction
All 15 tools (no gateway) 5,152 tokens
3 granted tools ~1,030 tokens −80%
5 granted tools ~1,717 tokens −67%
10 granted tools ~3,435 tokens −33%

Hemmabo token-cost questions.

How many tokens does the Hemmabo MCP server use?+

Its 15 tool definitions total 5,152 tokens — 2.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 Hemmabo 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 Hemmabo's token usage?+

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

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

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