Home / Token cost / Seneschal Data

The Seneschal Data MCP server costs 4,692 tokens before the first call.

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

QUICK ANSWER The Seneschal Data MCP server's tool definitions consume 4,692 tokens — 2.5× the median MCP server (1,905 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

MEASURED FROM SCHEMAS 19 tools · 4,692 tokens · 2.3% 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.3%
1M WINDOW 0.5%

Corpus context: Seneschal Data ranks #1062 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 4,692 tokens go.

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

ToolCategoryTokens% of server
seneschal_list_borrowers Read 461 9.8%
seneschal_private_watch_create Read 391 8.3%
seneschal_premium_opportunities Read 366 7.8%
seneschal_q Read 362 7.7%
seneschal_private_watch_topup_crypto Read 343 7.3%
seneschal_get_borrower_history Read 339 7.2%
seneschal_private_watch_historical Read 306 6.5%
seneschal_private_watch_topup Read 280 6.0%
seneschal_list_at_risk_borrowers Read 270 5.8%
seneschal_private_watch_derive_viewkey Read 260 5.5%
seneschal_premium_builder_stats Read 239 5.1%
seneschal_recent_liquidations Read 223 4.8%
seneschal_flashloan_providers Read 222 4.7%
seneschal_builder_leaderboard Read 164 3.5%
seneschal_paywall_info Read 117 2.5%
seneschal_stats_overview Read 117 2.5%
seneschal_get_borrower Read 111 2.4%
seneschal_private_watch_info Read 68 1.4%
seneschal_health Read 53 1.1%

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

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

Grant scopeDefinition costReduction
All 19 tools (no gateway) 4,692 tokens
3 granted tools ~741 tokens −84%
5 granted tools ~1,235 tokens −74%
10 granted tools ~2,469 tokens −47%

Seneschal Data token-cost questions.

How many tokens does the Seneschal Data MCP server use?+

Its 19 tool definitions total 4,692 tokens — 2.3% 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 Seneschal Data 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 Seneschal Data's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Seneschal Data 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 741 tokens, a 84% 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 19 catalogued Seneschal Data tools. Counts refresh with every site build.

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

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