Home / Token cost / Sui

The Sui MCP server costs 3,762 tokens before the first call.

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

QUICK ANSWER The Sui MCP server's tool definitions consume 3,762 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 53 tools · 3,762 tokens · 1.9% 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.9%
1M WINDOW 0.4%

Corpus context: Sui ranks #1184 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,762 tokens go.

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

ToolCategoryTokens% of server
query_transactions Read 170 4.5%
query_events Read 142 3.8%
swap_quote Read 134 3.6%
cetus_get_pools Read 126 3.3%
dev_inspect Read 117 3.1%
move_call Write 113 3.0%
get_object Read 104 2.8%
split_coins Read 102 2.7%
merge_coins Write 100 2.7%
get_owned_objects Read 99 2.6%
transfer_sui Financial 97 2.6%
get_transaction Read 95 2.5%
multi_get_objects Read 95 2.5%
get_coins Read 94 2.5%
transfer_objects Financial 88 2.3%
get_token_price Read 85 2.3%
get_move_struct Read 84 2.2%
request_add_stake Write 83 2.2%
import_wallet Write 81 2.2%
get_move_function Read 78 2.1%
get_epoch_info Read 74 2.0%
get_object_history Read 70 1.9%
get_normalized_module Read 69 1.8%
get_coin_metadata Read 68 1.8%
suins_get_price Read 68 1.8%
request_withdraw_stake Financial 65 1.7%
get_dynamic_fields Read 65 1.7%
suins_get_name_record Read 65 1.7%
create_wallet Write 64 1.7%
deepbook_get_pool Read 60 1.6%
switch_network Write 59 1.6%
cetus_get_pool Read 55 1.5%
get_all_balances Read 54 1.4%
resolve_name Write 54 1.4%
get_package_modules Read 52 1.4%
dry_run_transaction Execute 51 1.4%
list_common_tokens Read 51 1.4%
request_faucet Read 51 1.4%
resolve_address Write 49 1.3%
get_balance Read 48 1.3%
get_checkpoint Read 45 1.2%
get_committee_info Read 45 1.2%
get_total_supply Read 45 1.2%
get_stakes Read 44 1.2%
get_system_state Read 42 1.1%
get_network_info Read 37 1.0%
get_protocol_config Read 37 1.0%
get_move_call_metrics Read 36 1.0%
get_validators Read 35 0.9%
get_total_transactions Read 31 0.8%
get_reference_gas_price Read 29 0.8%
list_wallets Read 29 0.8%
get_latest_checkpoint Read 28 0.7%

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

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

Grant scopeDefinition costReduction
All 53 tools (no gateway) 3,762 tokens
3 granted tools ~213 tokens −94%
5 granted tools ~355 tokens −91%
10 granted tools ~710 tokens −81%

Sui token-cost questions.

How many tokens does the Sui MCP server use?+

Its 53 tool definitions total 3,762 tokens — 1.9% 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 Sui 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 Sui's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Sui 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 213 tokens, a 94% 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 53 catalogued Sui tools. Counts refresh with every site build.

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

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