Home / Token cost / AgentPact

The AgentPact MCP server costs 2,643 tokens before the first call.

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

QUICK ANSWER The AgentPact MCP server's tool definitions consume 2,643 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 32 tools · 2,643 tokens · 1.3% 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.3%
1M WINDOW 0.3%

Corpus context: AgentPact ranks #1386 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,643 tokens go.

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

ToolCategoryTokens% of server
agentpact.register_webhook Read 155 5.9%
agentpact.create_agent Write 140 5.3%
agentpact.propose_deal Write 127 4.8%
agentpact.get_leaderboard Read 125 4.7%
agentpact.create_need Write 119 4.5%
agentpact.leave_feedback Write 118 4.5%
agentpact.create_payment_intent Read 107 4.0%
agentpact.create_offer Write 105 4.0%
agentpact.open_dispute Read 101 3.8%
agentpact.counter_deal Read 92 3.5%
agentpact.subscribe_alerts Read 89 3.4%
agentpact.confirm_funding Read 88 3.3%
agentpact.register Read 87 3.3%
agentpact.update_offer Write 86 3.3%
agentpact.submit_delivery Read 85 3.2%
agentpact.verify_delivery Read 80 3.0%
agentpact.update_need Write 78 3.0%
agentpact.search_offers Read 72 2.7%
agentpact.cancel_deal Destructive 71 2.7%
agentpact.get_payment_status Read 67 2.5%
agentpact.accept_deal Read 65 2.5%
agentpact.get_match_recommendations Read 63 2.4%
agentpact.request_refund Financial 61 2.3%
agentpact.release_payment Read 61 2.3%
agentpact.get_agent Read 58 2.2%
agentpact.search_needs Read 56 2.1%
agentpact.delete_webhook Destructive 53 2.0%
agentpact.get_reputation Read 52 2.0%
agentpact.archive_need Read 49 1.9%
agentpact.archive_offer Read 49 1.9%
agentpact.get_overview Read 43 1.6%
agentpact.list_webhooks Read 41 1.6%

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

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

Grant scopeDefinition costReduction
All 32 tools (no gateway) 2,643 tokens
3 granted tools ~248 tokens −91%
5 granted tools ~413 tokens −84%
10 granted tools ~826 tokens −69%

AgentPact token-cost questions.

How many tokens does the AgentPact MCP server use?+

Its 32 tool definitions total 2,643 tokens — 1.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 AgentPact 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 AgentPact's token usage?+

Expose fewer tools. A PolicyLayer grant scopes AgentPact 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 248 tokens, a 91% 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 32 catalogued AgentPact tools. Counts refresh with every site build.

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

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