Home / Token cost / Autoform

The Autoform MCP server costs 6,160 tokens before the first call.

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

QUICK ANSWER The Autoform MCP server's tool definitions consume 6,160 tokens — 3.2× the median MCP server (1,905 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

MEASURED FROM SCHEMAS 11 tools · 6,160 tokens · 3.1% of 200k · 0.6% 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 3.1%
1M WINDOW 0.6%

Corpus context: Autoform ranks #953 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 6,160 tokens go.

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

ToolCategoryTokens% of server
autoform_fill_batch_at_coordinates Write 1,164 18.9%
autoform_analyze_static_pdf Read 830 13.5%
autoform_fill_batch_acroform Write 789 12.8%
autoform_generate_batch Write 761 12.4%
autoform_fill_at_coordinates Write 656 10.6%
autoform_detect_fields Read 530 8.6%
autoform_save_coordinates_as_template Write 494 8.0%
autoform_fill_pdf Write 441 7.2%
autoform_import_template Write 205 3.3%
autoform_get_pdf_info Read 147 2.4%
autoform_list_templates Read 143 2.3%

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

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

Grant scopeDefinition costReduction
All 11 tools (no gateway) 6,160 tokens
3 granted tools ~1,680 tokens −73%
5 granted tools ~2,800 tokens −55%
10 granted tools ~5,600 tokens −9%

Autoform token-cost questions.

How many tokens does the Autoform MCP server use?+

Its 11 tool definitions total 6,160 tokens — 3.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 Autoform 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 Autoform's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Autoform 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 1,680 tokens, a 73% 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 11 catalogued Autoform tools. Counts refresh with every site build.

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

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