Skip to main content
Glama

Solana transaction explainer (free summary; full 0.005 USDC via x402)

explain_tx
Read-only

Plain-language explanation of a Solana transaction from one getTransaction read: status, fee, parsed actions (SOL and SPL/Token-2022 transfers, approvals, revokes, account creation and closures), best-effort swap descriptions for Jupiter, Raydium, Orca, Meteora and pump.fun, and Rugsight grades for tokens the transaction touched. Unknown programs are labelled unknown. Automated technical data, not financial advice, not a safety guarantee. The free summary (status, fee, short explanation, programs, movements, up to 3 mint grades) 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 have a Solana transaction signature and need a plain-language explanation of what it did, including Rugsight grades for tokens it touched.

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": {
      "signature": "<signature>"
    },
    "name": "explain_tx"
  }
}

Input Schema

NameRequiredDescriptionDefault
fullNoIf true, return the full paid explanation via x402 (0.005 USDC). The free summary is returned when this is omitted or false.
signatureYesSolana transaction signature (base58, 64 bytes)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes well beyond them by disclosing the 10-calls-per-day-per-IP rate limit, the 0.005 USDC x402 payment handshake ('call once to receive the PaymentRequired object, then retry with _meta["x402/payment"]'), the best-effort nature of swap descriptions, and explicit disclaimers that output is not financial advice or a safety guarantee.

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 capability and tightly packed, and the usage trigger is placed last correctly. It is dense and slightly repetitive, listing the free-summary contents after already enumerating the explanation's components, and restating the 0.005 USDC x402 price twice, which costs a bit of space.

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 read-only, open-world tool with no output schema, this covers everything an agent needs: input meaning, both cost tiers, the exact payment retry protocol, rate limiting, the limits of the analysis (best-effort swaps, unknown programs), and disclaimers about what the result does not guarantee.

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%, so the baseline is 3, but the description adds real meaning: it explains that full=true triggers the paid x402 path at 0.005 USDC and that omitting/false yields the free summary, and it clarifies that the signature is read via a single getTransaction call. Little is added for the signature's format, but the schema already covers that with a pattern.

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 ('plain-language explanation of a Solana transaction') and enumerates exactly what is covered: status, fee, parsed actions, swap descriptions for named DEXes, and Rugsight grades. It also sets scope boundaries ('Unknown programs are labelled unknown'), so an agent can tell this apart from the token-risk and wallet-scan siblings without opening a schema.

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

Usage Guidelines5/5

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

Ends with an explicit trigger condition: 'Use when you have a Solana transaction signature and need a plain-language explanation of what it did.' It also routes between the two modes, stating that the free summary is capped at 10 calls per day per IP and that full=true is the paid JSON at 0.005 USDC, with the exact two-step x402 retry procedure.

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