Skip to main content
Glama

Tx explain

tx_explain

Explain transaction. What did a Base or Arc transaction do? One plain sentence plus the function, every token moved and the gas in USD. $0.003 per call over x402.

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

Input Schema

NameRequiredDescriptionDefault
txYesthe transaction hash (0x + 64 hex)
chainYesbase or arc
paymentNoa signed x402 payment (the same base64 payload you would put in the PAYMENT-SIGNATURE header). Pass it here and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does disclose the two things an agent most needs: the cost ($0.003 per call over x402) and the fact that payment settles inside the call via the payment parameter. It does not cover failure modes (invalid hash, unsupported chain) or latency, which keeps it from 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?

The definition is short and front-loaded with the purpose before the output description and price. The opening two sentences ('Explain transaction.' and the question) partly restate each other, a small redundancy in an otherwise efficient block.

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?

There is no output schema, but the description compensates by enumerating what is returned (sentence, function, token movements, gas in USD). With only three well-documented parameters and a stated price model, an agent has enough to call it correctly; only error behavior is unaddressed.

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%, so every parameter is already documented, including the x402 payload format for payment. The description adds only the accepted chain values and the output composition, which is adequate but not meaningfully beyond the schema, so the baseline 3 applies.

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 gives a specific verb and resource ('Explain transaction') plus the exact output shape: one plain sentence, the function called, every token moved, and gas in USD. It scopes the tool to Base and Arc chains, which helps separate it from generic EVM siblings, though it never names those siblings 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 implied by the question 'What did a Base or Arc transaction do?', which tells an agent this is for post-hoc interpretation of a hash. There is no explicit when-not guidance and no mention of when to prefer evm_tx or x1_tx_explain instead, so selection between lookalike siblings is left to inference.

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