Skip to main content
Glama

tx_decode

Read-onlyIdempotent

Decode any EVM transaction: function call, parameters, token transfers, and plain-English explanation. Free over MCP for 10 calls per day; beyond that the tool returns the pay-per-call x402 endpoint and its price.

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

Input Schema

NameRequiredDescriptionDefault
chainNoBlockchain networkethereum
txHashYesTransaction hash (0x-prefixed, 64 hex chars)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive behavior. The description adds important beyond-annotation context: 10 free MCP calls per day and a pay-per-call x402 endpoint with price beyond that. It does not discuss authentication, but the paywall behavior is clearly disclosed.

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?

The description is two sentences with no waste. The primary purpose is front-loaded, and the free-call/paywall constraint follows as a relevant operational note.

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 simple two-parameter tool with rich annotations and no output schema, the description is mostly complete: it explains what is decoded and how quota/paywall behavior works. The missing piece is explicit sibling comparison, but the core call information is present.

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%, so txHash format and the chain enum are already documented in the schema. The description only implies EVM chain scope and adds no further parameter-level meaning, making the baseline 3 appropriate.

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 states a specific verb and resource: 'Decode any EVM transaction.' It also lists the decoded artifacts (function call, parameters, token transfers, plain-English explanation), and the 'EVM' qualifier distinguishes it from Solana transaction tools such as solana_tx_explain.

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 'any EVM transaction' and the free-call quota. However, there is no explicit guidance on when to choose this over tx_simulate or other siblings, and no when-not-use conditions.

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.