Skip to main content
Glama

xRoot token operations

Get fee estimate

get_fee_estimate
Read-onlyIdempotent

Quote the exact cost of a token operation before anything is built: the platform fee for that service on that chain plus the estimated network fee (rent, base and priority), as decimal strings in the chain's currency. Use it when a user asks what a token deploy, authority revoke, airdrop or metadata update would cost. Reads only; nothing is prepared or sent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesThe operation intent — same shape the browser flow sends (chain, then service, then the service's fields).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / request / properties / options / description
      Previous value: -"Service options, keyed by service. spl-token and token-2022 (optional, may be omitted): transferTaxBps, transferTaxMaxFee, permanentDelegate, freezeAuthority. authority-tools (REQUIRED): revokeMint, revokeFreeze, revokeUpdate as booleans — all three must be present, at least one true; optional revokePermanentDelegate, revokeTransferFee, revokeWithheldWithdraw, revokeTransferHook, revokePause. airdrop (REQUIRED): recipients, a list of {address, amount} — at most 20 recipients per transaction — with amount as a decimal string in whole tokens, the same unit as supply; the mint's decimals are applied at prepare time. update-metadata (REQUIRED, at least one): name, symbol, metadataUri."New value: +"Service options, keyed by service. spl-token (optional, may be omitted): freezeAuthority. token-2022 (optional, may be omitted): transferTaxBps, transferTaxMaxFee, permanentDelegate, freezeAuthority — a transfer tax and a permanent delegate exist only on token-2022, and spl-token refuses them. authority-tools (REQUIRED): revokeMint, revokeFreeze, revokeUpdate as booleans — all three must be present, at least one true; optional revokePermanentDelegate, revokeTransferFee, revokeWithheldWithdraw, revokeTransferHook, revokePause. airdrop (REQUIRED): recipients, a list of {address, amount} — at most 20 recipients per transaction — with amount as a decimal string in whole tokens, the same unit as supply; the mint's decimals are applied at prepare time. update-metadata (REQUIRED, at least one): name, symbol, metadataUri."
  2. Changed1 schema field changed
    • addedInput schema / properties / request / allOf
      Added value: +[
      +  {
      +    "if": {
      +      "properties": {
      +        "service": {
      +          "enum": [
      +            "spl-token",
      +            "token-2022"
      +          ]
      +        }
      +      },
      +      "required": [
      +        "service"
      +      ]
      +    },
      +    "then": {
      +      "required": [
      +        "token"
      +      ]
      +    }
      +  },
      +  {
      +    "if": {
      +      "properties": {
      +        "service": {
      +          "enum": [
      +            "authority-tools",
      +            "airdrop",
      +            "update-metadata"
      +          ]
      +        }
      +      },
      +      "required": [
      +        "service"
      +      ]
      +    },
      +    "then": {
      +      "required": [
      +        "tokenAddress",
      +        "options"
      +      ]
      +    }
      +  }
      +]
  3. Changed2 schema fields changed
    • changedInput schema / properties / request / properties / options / description
      Previous value: -"Service options, keyed by service. spl-token and token-2022 (optional, may be omitted): transferTaxBps, transferTaxMaxFee, permanentDelegate, freezeAuthority. authority-tools (REQUIRED): revokeMint, revokeFreeze, revokeUpdate as booleans — all three must be present, at least one true; optional revokePermanentDelegate, revokeTransferFee, revokeWithheldWithdraw, revokeTransferHook, revokePause. airdrop (REQUIRED): recipients, a list of {address, amount} with amount as a decimal string in whole tokens, the same unit as supply — the mint's decimals are applied at prepare time. update-metadata (REQUIRED, at least one): name, symbol, metadataUri."New value: +"Service options, keyed by service. spl-token and token-2022 (optional, may be omitted): transferTaxBps, transferTaxMaxFee, permanentDelegate, freezeAuthority. authority-tools (REQUIRED): revokeMint, revokeFreeze, revokeUpdate as booleans — all three must be present, at least one true; optional revokePermanentDelegate, revokeTransferFee, revokeWithheldWithdraw, revokeTransferHook, revokePause. airdrop (REQUIRED): recipients, a list of {address, amount} — at most 20 recipients per transaction — with amount as a decimal string in whole tokens, the same unit as supply; the mint's decimals are applied at prepare time. update-metadata (REQUIRED, at least one): name, symbol, metadataUri."
    • changedInput schema / properties / request / properties / token / properties / supply / description
      Previous value: -"Total supply as a decimal string in base units, e.g. \"1000000000\" for 1B tokens."New value: +"Total supply in whole tokens as a decimal string, e.g. \"1000000000\" for 1B tokens — the mint's decimals are applied at prepare time."
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is partly covered, but the description adds meaningful context beyond them: 'nothing is prepared or sent' clarifies no transaction is staged, and it discloses the shape of the returned values (decimal strings in the chain's currency). It does not mention rate limits or error cases, so it stops short of 5.

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

Conciseness5/5

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

Two sentences, no filler. The cost composition is front-loaded, the usage trigger follows, and the read-only guarantee closes. Every clause carries information.

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

Completeness5/5

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

For a single-parameter, read-only quoting tool with no output schema, the description supplies what the schema cannot: it explains that the response is decimal-string fee components in the chain's currency, so the agent does not need an output schema to interpret results. Nothing material is missing.

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

Parameters4/5

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

Schema coverage is 100% and the nested request object is exhaustively documented per service, so the baseline would be 3. The description adds modest but real value by correlating the quote to 'that service on that chain' and enumerating the four operation categories (deploy, revoke, airdrop, metadata update) that map onto the service enum, helping an agent frame the request correctly.

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?

The description states a specific verb and resource — 'Quote the exact cost of a token operation' — and itemizes what the quote contains (platform fee for that service on that chain plus estimated network fee: rent, base and priority). An agent can distinguish it from all siblings, none of which produce cost quotes.

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?

It gives an explicit trigger: 'Use it when a user asks what a token deploy, authority revoke, airdrop or metadata update would cost,' which maps the caller's intent to the tool. There is no 'when-not' guidance or named alternative, but no sibling occupies this functional space, so the omission is low-risk.

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