Skip to main content
Glama

solana_tx_explain

Read-onlyIdempotent

Explain a Solana transaction in plain English: labeled programs, token/SOL movements, success status, and risk flags. Free over MCP for 10 calls per day; beyond that the tool returns the pay-per-call x402 endpoint and its price.

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": "solana_tx_explain"
  }
}

Input Schema

NameRequiredDescriptionDefault
signatureYesBase58 Solana transaction signature

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and open-world behavior, so the bar is lower, but the description still adds real value by disclosing the 10-calls-per-day free quota and the unusual fallback where the tool returns a pay-per-call x402 endpoint and price instead of an explanation. It does not say what is returned for an unknown or failed signature, which is the remaining behavioral gap.

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, and the capability statement is front-loaded before the quota caveat. Every clause earns its place by either defining output or warning about the paywall.

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?

For a one-parameter read tool with full annotations and no output schema, the description does the necessary work: it lists what the explanation contains and warns about the quota/paywall path. Only the error and not-found behavior is left unstated, a minor gap given the tool's simplicity.

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?

There is a single parameter with 100% schema description coverage ("Base58 Solana transaction signature"), so the schema already carries the meaning. The description adds nothing about signature format, accepted transaction versions, or lookup behavior beyond what the schema states, which is the expected baseline for full coverage.

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

Purpose4/5

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

The description opens with a specific verb and resource ("Explain a Solana transaction") and enumerates the output content: labeled programs, token/SOL movements, success status, risk flags. That is far more concrete than a sibling like tx_decode or tx_simulate, though it never names those siblings to draw the boundary explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: you call this to understand an already-existing transaction rather than to simulate or decode raw data. There is no explicit statement of when to prefer it over solana_tx_simulate, tx_simulate, or tx_decode, and no prerequisites (e.g., whether the transaction must be confirmed) are given.

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.