Home / Token cost / Betterdb

The Betterdb MCP server costs 5,348 tokens before the first call.

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

QUICK ANSWER The Betterdb MCP server's tool definitions consume 5,348 tokens — 2.8× the median MCP server (1,905 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

MEASURED FROM SCHEMAS 41 tools · 5,348 tokens · 2.7% 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.7%
1M WINDOW 0.5%

Corpus context: Betterdb ranks #1003 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,348 tokens go.

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

ToolCategoryTokens% of server
cache_propose_invalidate Read 329 6.2%
cache_propose_threshold_adjust Read 234 4.4%
cache_propose_tool_ttl_adjust Read 232 4.3%
get_hot_keys Read 200 3.7%
cache_threshold_recommendation Read 191 3.6%
cache_similarity_distribution Read 183 3.4%
cache_edit_and_approve_proposal Write 180 3.4%
get_acl_audit Read 175 3.3%
cache_recent_changes Read 168 3.1%
get_commandlog_history Read 168 3.1%
add_connection Write 164 3.1%
get_slot_stats Read 158 3.0%
test_connection Read 144 2.7%
get_anomalies Read 142 2.7%
get_client_activity Read 142 2.7%
cache_list_pending_proposals Read 140 2.6%
cache_health Read 138 2.6%
get_commandlog_patterns Read 136 2.5%
cache_tool_effectiveness Read 135 2.5%
get_info Read 130 2.4%
get_latency_history Read 130 2.4%
start_monitor Execute 129 2.4%
cache_approve_proposal Write 124 2.3%
cache_reject_proposal Write 120 2.2%
get_cluster_slowlog Read 111 2.1%
get_slowlog_patterns Read 110 2.1%
get_health Read 107 2.0%
get_commandlog Read 91 1.7%
cache_list Read 88 1.6%
get_cluster_nodes Read 87 1.6%
get_cluster_node_stats Read 86 1.6%
set_default_connection Write 82 1.5%
get_slowlog Read 80 1.5%
cache_get_proposal Read 79 1.5%
select_instance Write 77 1.4%
remove_connection Destructive 75 1.4%
get_memory Read 61 1.1%
stop_monitor Execute 57 1.1%
get_clients Read 56 1.0%
get_latency Read 56 1.0%
list_instances Read 53 1.0%

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

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

Grant scopeDefinition costReduction
All 41 tools (no gateway) 5,348 tokens
3 granted tools ~391 tokens −93%
5 granted tools ~652 tokens −88%
10 granted tools ~1,304 tokens −76%

Betterdb token-cost questions.

How many tokens does the Betterdb MCP server use?+

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

Expose fewer tools. A PolicyLayer grant scopes Betterdb 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 391 tokens, a 93% 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 41 catalogued Betterdb tools. Counts refresh with every site build.

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

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