Skip to main content
Glama

Solana Token-2022 transfer preview (free summary; full 0.005 USDC via x402)

preview_receive
Read-only

Deterministic preview of a Solana Token-2022 transfer: the current on-chain transfer fee (basis points and maximum), the net amount the recipient receives, and flags for a transfer hook, freeze authority, permanent delegate, default-frozen accounts or a pause authority. Models a transfer only, not a swap or DEX pool fee. Does not execute or audit a hook program. Automated technical data, not financial advice. The free summary (net amount, fee, up to 3 flags) is limited to 10 calls per day per IP. Pass full=true for the full JSON at 0.005 USDC via x402: call once to receive the PaymentRequired object, then retry with _meta["x402/payment"]. Use when you need the net amount a Token-2022 transfer will deliver after the current on-chain transfer fee.

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": {
      "mint": "<mint>",
      "amount": "<amount>"
    },
    "name": "preview_receive"
  }
}

Input Schema

NameRequiredDescriptionDefault
fullNoIf true, return the full paid preview via x402 (0.005 USDC). The free summary is returned when this is omitted or false.
mintYesSolana token mint address (base58)
amountYesAmount to send, in UI token units (positive decimal)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description independently discloses the free-tier cap of 10 calls per day per IP, the paid tier price and the two-step x402 handshake (call once for a PaymentRequired object, retry with _meta['x402/payment']), and the truncation of flags to 3 in the free summary. These are substantive operational facts an agent must know before invoking. It stops short of 5 only because latency or failure behavior of the payment retry is not covered.

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?

Front-loaded with the core purpose and output contents, followed by scope limits, then the free/paid mechanics, so the reader hits the essential facts first. Several clauses are load-bearing, though 'Automated technical data, not financial advice' and the repeated restatement of what is free versus paid add length without much decision value.

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?

There is no output schema, and the description compensates fully by naming the returned fields and the exact difference between the free summary and the full paid JSON. Given the dual payment mode and the rate limit, an agent has everything needed to decide, call, and interpret a result.

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%, so mint, amount and full are already documented in the schema, establishing a baseline of 3. The description adds genuine meaning for full=true by spelling out the payment retry mechanics that the schema only gestures at, but mint and amount receive no interpretation beyond their schema text.

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 — 'Deterministic preview of a Solana Token-2022 transfer' — and enumerates exactly what is returned (transfer fee in bps and max, net amount to recipient, hook/freeze/delegate/pause flags). It also scopes itself against adjacent concepts ('Models a transfer only, not a swap or DEX pool fee'), so an agent can tell it apart from risk-report or tx-explainer siblings without opening any schema.

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 an explicit use case ('Use when you need the net amount a Token-2022 transfer will deliver after the current on-chain transfer fee') and several explicit exclusions (not a swap or DEX pool fee, does not execute, does not audit a hook program). What it lacks is routing to a named alternative when a sibling tool would be more appropriate, which keeps it short of a 5.

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