Home / Token cost / JustCall

The JustCall MCP server costs 3,578 tokens before the first call.

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

QUICK ANSWER The JustCall MCP server's tool definitions consume 3,578 tokens — around the median MCP server (1,905 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

MEASURED FROM SCHEMAS 29 tools · 3,578 tokens · 1.8% 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 1.8%
1M WINDOW 0.4%

Corpus context: JustCall ranks #1214 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 3,578 tokens go.

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

ToolCategoryTokens% of server
list_calls Read 695 19.4%
create_campaign Write 300 8.4%
create_contact Write 285 8.0%
update_campaign Write 245 6.8%
list_contacts Read 187 5.2%
list_campaigns Read 168 4.7%
get_sales_dialer_analytics Read 131 3.7%
list_numbers Read 119 3.3%
get_call Read 115 3.2%
list_sms Read 112 3.1%
send_sms Write 97 2.7%
list_webhooks Read 96 2.7%
create_webhook Write 96 2.7%
get_number_analytics Read 88 2.5%
get_agent_analytics Read 80 2.2%
check_sms_reply Read 79 2.2%
list_users Read 79 2.2%
update_call Write 79 2.2%
get_account_analytics Read 64 1.8%
create_sms_tag Write 61 1.7%
list_sms_tags Read 58 1.6%
get_number Read 44 1.2%
get_sms Read 44 1.2%
get_call_journey Read 43 1.2%
get_campaign Read 43 1.2%
get_sms_tag Read 43 1.2%
get_voice_agent_data Read 43 1.2%
delete_sms_tag Destructive 42 1.2%
get_user Read 42 1.2%

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

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

Grant scopeDefinition costReduction
All 29 tools (no gateway) 3,578 tokens
3 granted tools ~370 tokens −90%
5 granted tools ~617 tokens −83%
10 granted tools ~1,234 tokens −66%

JustCall token-cost questions.

How many tokens does the JustCall MCP server use?+

Its 29 tool definitions total 3,578 tokens — 1.8% 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 JustCall 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 JustCall's token usage?+

Expose fewer tools. A PolicyLayer grant scopes JustCall 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 370 tokens, a 90% 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 29 catalogued JustCall tools. Counts refresh with every site build.

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

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