Skip to main content
Glama

Transaction Explainer

explain_transaction

Plain-words explanation of one Ethereum or Base transaction: a one-line summary (swap, send, approval, bridge, deposit, NFT transfer, failed call), every token and NFT movement with symbols, the account's net change, approvals (incl. Permit2), protocols touched, and red flags: unlimited or wallet approvals, look-alike tokens, address-poisoning spam, failed calls. Handles smart-account (ERC-4337) and gasless USDC (EIP-3009 / x402) transactions. Costs $0.01 (x402, USDC).

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

Input Schema

NameRequiredDescriptionDefault
hashYesTransaction hash, 0x followed by 64 hex characters
chainYesChain: ethereum, base

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does add real context: per-call cost of $0.01 paid in USDC via x402, the two supported chains, and coverage of smart-account (ERC-4337) and gasless USDC (EIP-3009/x402) transactions. It lacks rate limits, latency, and behavior on a not-yet-mined or unknown hash.

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?

Purpose is front-loaded in the first clause, followed by a dense but useful enumeration of returned content and cost. It is a single long run-on sentence, but nearly every element earns its place.

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?

Because there is no output schema, the description must describe the return payload — and it does so thoroughly, down to red-flag categories and the cost. The main gap for a 2-parameter, paid tool is the absence of any guidance on when to prefer tx_status instead.

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% — hash format (0x + 64 hex) and the chain values are already documented in the schema. The description only reinforces the chain set ('Ethereum or Base') and adds nothing about edge cases like a hash from the wrong chain, 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?

States a specific verb and resource — 'Plain-words explanation of one Ethereum or Base transaction' — and then enumerates exactly what the explanation contains (token/NFT movements, net change, approvals incl. Permit2, protocols, red flags). That enumeration separates it in practice from a status-checking sibling like tx_status 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 only implied: the agent can infer this is the tool for interpreting a known transaction hash on ethereum or base. There is no explicit when-to-use versus tx_status, no stated prerequisites (e.g. must the hash be confirmed/mined first), and no exclusions.

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