Skip to main content
Glama

zato: Ethereum & Base Data API (pay-per-call x402)

Ethereum transaction details by hash

eth_tx
Read-only

Ethereum transaction details by hash: status (success/failed/pending), block, from/to, ETH value, gas used, effective gas price, fee in ETH and number of ERC-20 Transfer events. Ethereum mainnet, public RPC data. Price: $0.001 USDC per call (x402 v2, Base). Free demo: https://api.zato.org/demo/eth/tx

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

Input Schema

NameRequiredDescriptionDefault
hashYesTransaction hash

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?

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful operational context beyond that: the data source (public RPC), the price ($0.001 USDC per call via x402 v2 on Base), and a free demo URL. It stops short of disclosing failure modes such as unknown-hash behavior or pending-transaction handling.

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?

Two compact blocks with the payload details front-loaded and pricing/demo information trailing, with no filler prose. The price and demo sentences are operationally useful rather than padding.

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 one-parameter read tool with no output schema, the description compensates well by enumerating the returned fields, naming the chain and data source, and stating cost. Minor gaps remain around error/not-found cases and whether Transfer event counting is capped.

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 the hash parameter carries its own type, 0x-prefixed 64-hex pattern, and description, so the schema does the heavy lifting. The description only restates 'by hash' and adds no format, casing, or normalization guidance beyond the schema.

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+resource ('Ethereum transaction details by hash') and enumerates exactly what is returned (status, block, from/to, value, gas used, fee, Transfer event count). The phrase 'Ethereum mainnet' explicitly separates it from the sibling base_tx, which covers the other chain.

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?

Scope is implied by 'Ethereum mainnet, public RPC data' and 'by hash', which lets an agent infer this is a single-transaction lookup rather than a wallet or contract tool. However, there is no explicit statement of when to use this versus base_tx or eth_contract, and no prerequisites or exclusions are given.

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