Skip to main content
Glama

Solana Signal

Explain a Solana transaction

tx_explain
Read-only

Decode any Solana transaction signature: status, fee, action type (swap/transfer), human-readable swap summary, programs used (Jupiter, Raydium, pump.fun, Orca, Meteora...), SOL and token balance changes per owner. Free tier 20/day per IP.

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

Input Schema

NameRequiredDescriptionDefault
signatureYesTransaction signature (base58)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds genuinely new context — the free-tier quota of 20 calls/day per IP, the set of recognized programs (Jupiter, Raydium, pump.fun, Orca, Meteora), and the granularity of balance changes. It stops short of describing behavior for unknown programs, failed transactions, or invalid signatures, which keeps it off a 5.

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?

One colon-led sentence front-loads the verb and the return payload, followed by a short quota note that is genuinely useful. Dense but every clause carries information; the trailing '...' program list is the only slightly loose element.

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 correctly shoulders the burden of enumerating returned fields, and it also covers quota and program coverage for a one-parameter tool. Only edge-case behavior (signature not found, unparseable transaction) is unaddressed, a minor gap for a read-only decoder.

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?

The single parameter has 100% schema coverage including a base58 regex, so the schema already does the work. 'Any Solana transaction signature' only restates the parameter's meaning without adding format, length, or lookup-failure semantics beyond what the schema provides.

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 ('Decode') and resource ('Solana transaction signature') and then enumerates the exact outputs: status, fee, action type, swap summary, programs, per-owner balance changes. An agent immediately knows what it gets back, and none of the siblings (token_prices, token_risk, pump_new_launches) overlap with this function.

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?

The phrase 'Decode any Solana transaction signature' establishes the clear trigger condition: you have a signature and want it interpreted. There is no explicit when-not guidance or named alternative, but the sibling set contains no competing decode/lookup tool, so the omission costs little.

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