Home / Token cost / Cap Rate Signals

The Cap Rate Signals MCP server costs 4,296 tokens before the first call.

Connect Cap Rate Signals and its 14 tool definitions are loaded into the model's context on every request — 2.1% of a 200k window spent before your agent does anything.

QUICK ANSWER The Cap Rate Signals MCP server's tool definitions consume 4,296 tokens — 2.3× the median MCP server (1,905 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

MEASURED FROM SCHEMAS 14 tools · 4,296 tokens · 2.1% of 200k · 0.4% 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.1%
1M WINDOW 0.4%

Corpus context: Cap Rate Signals ranks #1105 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,296 tokens go.

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

ToolCategoryTokens% of server
find_metros Read 911 21.2%
get_top_picks Read 707 16.5%
get_metro_brief Read 624 14.5%
get_alerts Read 317 7.4%
get_regional_comps Read 287 6.7%
get_metro_map_data Read 281 6.5%
set_published_tier Write 230 5.4%
compare_metros Read 225 5.2%
get_weekly_review Read 177 4.1%
clear_stale_progress_flag Destructive 159 3.7%
get_tier Read 129 3.0%
assess_metro Read 113 2.6%
log_missed_query Read 95 2.2%
ping Execute 41 1.0%

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

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

Grant scopeDefinition costReduction
All 14 tools (no gateway) 4,296 tokens
3 granted tools ~921 tokens −79%
5 granted tools ~1,534 tokens −64%
10 granted tools ~3,069 tokens −29%

Cap Rate Signals token-cost questions.

How many tokens does the Cap Rate Signals MCP server use?+

Its 14 tool definitions total 4,296 tokens — 2.1% 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 Cap Rate Signals 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 Cap Rate Signals's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Cap Rate Signals 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 921 tokens, a 79% 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 14 catalogued Cap Rate Signals tools. Counts refresh with every site build.

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

A PolicyLayer grant scopes Cap Rate Signals 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.