Skip to main content
Glama

tx_hash_decoder

Decode an EVM transaction: status, fee, method selector, ERC-20 transfers and approvals

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

Input Schema

NameRequiredDescriptionDefault
hashYesTransaction hash (0x + 64 hex)
chainNoChain: base|ethereum|arbitrum|optimism (default base)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses the decoded payload (including ERC-20 transfers and approvals) but says nothing about read-only nature, error behavior for unknown hashes, unsupported chains, or response limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero filler; the returned fields come immediately after the verb, which is exactly where an agent scans.

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?

For a two-parameter read-only decoder with no output schema, the description compensates well by naming the decoded fields. It falls short only on failure modes and on clarifying per-chain behavior, both of which an agent might need.

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 description coverage is 100% and both parameters (hash format, chain enum with default base) are documented there, establishing the baseline of 3. The description adds no parameter-level meaning, such as what happens when chain is omitted or whether the chain alters decoding.

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?

Specific verb ("Decode") plus resource ("an EVM transaction") plus an enumeration of the returned data (status, fee, method selector, ERC-20 transfers and approvals). None of the sibling tools decodes transactions, so an agent can route here unambiguously.

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: an agent infers it should call this when holding a transaction hash. There is no explicit when-to-use, when-not-to-use, or pointer to a related sibling (e.g. token_safety_composite for a token seen in the transfers).

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