Skip to main content
Glama

Ballistic

Estimate the platform fee

estimate_fee
Read-onlyIdempotent

Estimate Ballistic’s platform fee for an amount leaving launch wallets. The fee is on what leaves the wallets, not on trading volume. Gives a figure for Solana and for a stable-coin amount; on BNB Chain and Robinhood Chain it gives the rate only. No account is read. Read-only arithmetic.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "withdrawn": "<withdrawn>"
    },
    "name": "estimate_fee"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNonative_out (default): the chain’s coin leaving launch wallets. stable_amount: a set stable-coin amount. primary_wallet: a withdrawal from the Primary wallet. unspent_funding: funding taken back with Recover.
chainNoWhich chain the launch wallets are on. Required for native_out. No chain is assumed.
volumeNoOptional. Buy and sell volume traded before withdrawing. It adds no platform fee.
withdrawnYesThe amount that leaves the launch wallets (after gas), not the amount that arrives.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so 'Read-only arithmetic. No account is read.' largely restates them, though the no-account/auth point is mildly useful. The genuinely additive disclosure is the per-chain result shape (figure vs rate only), which matters because there is no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short, front-loaded sentences: purpose, then the fee-base constraint, then outputs by chain, then safety. The only waste is the closing 'No account is read. Read-only arithmetic.', which duplicates the annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description appropriately explains what comes back per chain (a figure for Solana and stable-coin, rate-only for BNB Chain and Robinhood Chain). Combined with the 100%-documented input schema, an agent has enough to call it correctly; the omission of the native_out chain requirement is minor since the schema marks it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and both enum parameters plus 'withdrawn' are already well documented in the schema. The description reinforces the key semantic that the fee is computed on the withdrawn amount and not on `volume`, which is a small but real assist above baseline rather than new parameter-level detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Estimate Ballistic's platform fee') and immediately narrows the base to 'an amount leaving launch wallets', explicitly ruling out trading volume. That fee-base distinction is what makes it distinguishable from a generic pricing/limits lookup in the sibling set.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context for calling it (an amount is leaving launch wallets) and states the chain-dependent outcome, so an agent knows Solana/stable-coin returns a figure while BNB Chain and Robinhood Chain return only a rate. It stops short of naming an explicit alternative or a when-not-to-use case.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources