Skip to main content
Glama

Transaction explainer (x402)

chain_transaction_explain

Read-onlyIdempotent

$0.005 via x402: decode any transaction by hash into a plain-English explanation — what actually happened (a swap, transfer, approval, mint, or contract call), who the actors are, and the full list of asset changes (every native coin and token in/out with symbol, amount and direction), plus status, fee and the decoded method. The read agents make to UNDERSTAND a tx, not just confirm it landed: for wallet UX, accounting, risk, dispute and trading agents. Across Base, Ethereum, Optimism, Arbitrum, Polygon, Gnosis. Live from Blockscout; one paid call instead of running your own indexer + ABI decoder.

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": {
      "hash": "<hash>"
    },
    "name": "chain_transaction_explain"
  }
}

Input Schema

NameRequiredDescriptionDefault
hashYesTransaction hash (0x... 64 hex)
chainNobase|ethereum|optimism|arbitrum|polygon|gnosis (default base)
x_paymentNox402 payment payload (base64) to settle this call; omit to receive the payment terms first

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld and idempotent, and the description adds real behavioral facts on top: a concrete cost ($0.005 via x402), that payment must be settled for the call, the live data source (Blockscout), and the value framing versus self-hosting an indexer plus ABI decoder. It does not cover failure modes, rate limits, or what happens when a tx is not found, 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?

Front-loads price, purpose and outputs in a single dense paragraph with no filler sentences, and every clause carries information. It is somewhat overlong and promotional in tone ('one paid call instead of running your own indexer + ABI decoder'), which slightly hurts scanability but not correctness.

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 enumerating the returned fields (asset deltas with direction, status, fee, decoded method) and the supported chains. Combined with annotations covering the safety profile, an agent has everything needed to call it correctly.

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 description coverage is 100%, so the schema already documents hash format, chain values and the x_payment settlement flow, giving a baseline of 3. The description does add meaning by framing the hash as accepting 'any transaction' and reaffirming cross-chain scope, though it largely restates the chain list already present in the schema.

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 precise verb and resource: decode a transaction by hash into a plain-English explanation, then enumerates the exact outputs (what happened, actors, asset changes with symbol/amount/direction, status, fee, decoded method). It also draws a boundary against mere confirmation tools ('UNDERSTAND a tx, not just confirm it landed'), so an agent can distinguish it from sibling chain_* lookups without opening the 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 explicit usage context by naming the consuming agent roles (wallet UX, accounting, risk, dispute, trading) and contrasting understanding vs confirmation. It stops short of naming a specific sibling alternative or stating when NOT to use it, so it is clear context without full routing guidance.

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