Home / Token cost / Google Cloud Healthcare API Server

The Google Cloud Healthcare API Server MCP server costs 1,003 tokens before the first call.

Connect Google Cloud Healthcare API Server and its 15 tool definitions are loaded into the model's context on every request — 0.5% of a 200k window spent before your agent does anything.

QUICK ANSWER The Google Cloud Healthcare API Server MCP server's tool definitions consume 1,003 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 15 tools · 1,003 tokens · 0.5% 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.5%
1M WINDOW 0.1%

Corpus context: Google Cloud Healthcare API Server ranks #2192 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,003 tokens go.

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

ToolCategoryTokens% of server
get_patient_observations Read 111 11.1%
get_patient_careplans Read 92 9.2%
get_patient_allergies Read 89 8.9%
get_patient_encounters Read 88 8.8%
get_patient_procedures Read 85 8.5%
find_patient Read 73 7.3%
get_patient_conditions Read 67 6.7%
get_lab_results Read 64 6.4%
get_vital_signs Read 61 6.1%
get_appointments Read 59 5.9%
get_patient_medications Read 55 5.5%
get_medications_history Read 43 4.3%
search-pubmed Read 41 4.1%
search-trials Read 40 4.0%
get-drug-info Read 35 3.5%

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

Grant scopeDefinition costReduction
All 15 tools (no gateway) 1,003 tokens
3 granted tools ~201 tokens −80%
5 granted tools ~334 tokens −67%
10 granted tools ~669 tokens −33%

Google Cloud Healthcare API Server token-cost questions.

How many tokens does the Google Cloud Healthcare API Server MCP server use?+

Its 15 tool definitions total 1,003 tokens — 0.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 Google Cloud Healthcare API Server 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 Google Cloud Healthcare API Server's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Google Cloud Healthcare API Server 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 201 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 Google Cloud Healthcare API Server tools. Counts refresh with every site build.

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

A PolicyLayer grant scopes Google Cloud Healthcare API Server 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.