Skip to main content
Glama

Decode an EVM transaction: method, events, transfers

tx_decode
Read-only

Decoded EVM transaction on Base, Ethereum, Arbitrum, OP Mainnet, Polygon or Avalanche: status, block time, sender, target, value and fee in native coin and USD (current price), method and arguments, decoded events, ERC-20/721 token transfers, net token flows per address and a one-line summary. ABIs from Sourcify verified contracts or the Sourcify 4byte database. Ethereum receipts cover about the last 2 days. Sources: PublicNode and official chain JSON-RPC, Uniswap v3 pools. Price: $0.005 per successful call, paid in USDC with x402 v2; failed calls and calls that match nothing are not charged.

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

Input Schema

NameRequiredDescriptionDefault
hashYesTransaction hash (0x + 64 hex characters).
chainYesChain by name, alias or chain id: base (8453), ethereum (1), arbitrum (42161), optimism (10), polygon (137), avalanche (43114).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already mark it read-only and open-world, and the description adds substantial context beyond that: data provenance (PublicNode/official JSON-RPC, Uniswap v3 pools), how ABIs are resolved (Sourcify verified contracts or the 4byte database), a hard data-retention limit for Ethereum receipts, and a precise billing model ($0.005 per successful call in USDC via x402, failures and no-match calls free). These are exactly the operational facts an agent cannot get from structured fields.

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?

The output contents are front-loaded and every clause (sources, retention limit, pricing) carries information an agent needs. It is a dense, long single block rather than a short one, but nothing is filler; breaking pricing and limits into separate sentences would read better.

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?

With no output schema, the description takes on the burden of describing returns and does so comprehensively — fields, token flows, summary line — while also covering cost, provenance and a data-availability caveat. For a two-parameter read tool of this complexity, nothing material is missing.

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% and both parameters already document format and chain aliases/ids, so the schema carries the load. The description's chain list mirrors the schema's examples rather than adding new semantics such as hash format rules or behavior for unknown chains, so the baseline 3 applies.

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?

The description names a specific verb (decode) and resource (EVM transaction) and enumerates exactly what comes back — status, block time, sender, target, value/fee in native and USD, method and arguments, decoded events, ERC-20/721 transfers, net flows per address and a summary. That detail distinguishes it from a narrower sibling like chain_calldata_decode without needing to name it.

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 implied by the required (chain, hash) inputs and by the note that Ethereum receipts cover only about the last 2 days, which warns the agent off historical Ethereum lookups. However there is no explicit when-to-use vs alternatives guidance (e.g. how it differs from chain_sign_inspect or chain_calldata_decode), so the agent must infer routing.

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