Home / Token cost / Agentic Commerce Catalog

The Agentic Commerce Catalog MCP server costs 2,724 tokens before the first call.

Connect Agentic Commerce Catalog and its 22 tool definitions are loaded into the model's context on every request — 1.4% of a 200k window spent before your agent does anything.

QUICK ANSWER The Agentic Commerce Catalog MCP server's tool definitions consume 2,724 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 22 tools · 2,724 tokens · 1.4% of 200k · 0.3% 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.4%
1M WINDOW 0.3%

Corpus context: Agentic Commerce Catalog ranks #1352 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 2,724 tokens go.

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

ToolCategoryTokens% of server
create_music Write 306 11.2%
agent_music Read 242 8.9%
agent_video Read 205 7.5%
extend Read 169 6.2%
cover Read 165 6.1%
continue_track Read 125 4.6%
rig_oracle Read 118 4.3%
chain_chat Read 116 4.3%
voice_cover Read 115 4.2%
rig_analyze Read 113 4.1%
rights_lookup Read 106 3.9%
rig_roast Read 103 3.8%
style_coach Read 103 3.8%
audio_analyze Read 97 3.6%
lyric_sync Read 96 3.5%
lyrics Read 92 3.4%
wav_master Read 79 2.9%
midi Read 76 2.8%
stems_basic Read 75 2.8%
vox Read 75 2.8%
prompt_analyze Read 74 2.7%
stems_full Read 74 2.7%

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

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

Grant scopeDefinition costReduction
All 22 tools (no gateway) 2,724 tokens
3 granted tools ~371 tokens −86%
5 granted tools ~619 tokens −77%
10 granted tools ~1,238 tokens −55%

Agentic Commerce Catalog token-cost questions.

How many tokens does the Agentic Commerce Catalog MCP server use?+

Its 22 tool definitions total 2,724 tokens — 1.4% 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 Agentic Commerce Catalog 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 Agentic Commerce Catalog's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Agentic Commerce Catalog 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 371 tokens, a 86% 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 22 catalogued Agentic Commerce Catalog tools. Counts refresh with every site build.

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

A PolicyLayer grant scopes Agentic Commerce Catalog 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.