Skip to main content
Glama

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

Look up a Base transaction receipt

base_tx
Read-only

Base transaction details by hash. Public on-chain lookup of a Base (eip155:8453) transaction hash: status, block number, from/to, value in ETH, gas used and number of ERC-20 transfer logs. Public RPC data only. Price: $0.001 USDC per call (x402 v2, Base). Free demo: https://api.zato.org/demo/base/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": "base_tx"
  }
}

Input Schema

NameRequiredDescriptionDefault
hashYesTransaction hash

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/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 context beyond that: it enumerates the returned fields (status, block, from/to, ETH value, gas used, ERC-20 log count), states 'public RPC data only' (no auth needed), and discloses per-call pricing under x402 v2. It says nothing about error or not-found behavior, fee settlement, or rate limits, so it stops short of 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.

Conciseness3/5

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

Front-loaded with the action, but the single block mixes value (returned fields, public-data caveat) with promotional content — the pricing line and free-demo URL — that is only marginally relevant to invoking the tool correctly.

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?

With no output schema, listing the returned fields is the right compensation and makes the definition self-sufficient for a one-param read tool. Minor gaps remain around failure modes and whether a null/absent receipt is possible.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter, fully documented in the schema with a regex pattern — a 0-to-1-param tool with 100% coverage needs little help. The description adds only the notion that the hash identifies a transaction, which is close to what the schema already conveys.

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?

States a specific verb and resource ('Base transaction details by hash') and pins the chain explicitly as 'Base (eip155:8453)', which implicitly separates it from the eth_tx sibling. It does not name alternatives outright, but the chain scoping makes the domain unambiguous.

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 required input: supply a 32-byte tx hash to get receipt details. There is no explicit when-to-use vs when-not guidance, no mention of when a user should prefer eth_tx or base_contract instead, and no statement about what happens on an unknown or pending hash.

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