Skip to main content
Glama

zato crypto data

Full Ethereum transaction details by hash

tx
Read-only

One Ethereum transaction by hash: details plus receipt (status, gas, logs). Price: $0.002 USDC per call (x402, Base).

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

Input Schema

NameRequiredDescriptionDefault
hashYestransaction hash
networkNoethereum

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?

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered structurally. The description adds genuinely useful, non-schema context: a per-call price of $0.002 USDC via x402 on Base, which tells the agent this is a metered paid call, plus the fact that a receipt is bundled. It does not discuss failure modes for unknown hashes or pending transactions.

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?

Two tight sentences with zero filler: scope and return contents first, then the pricing constraint. Everything front-loaded and nothing repeated from the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with no output schema, the description covers what it returns (details plus receipt fields), which chain it applies to, and the payment model. Nothing an agent needs in order to call it or budget for it is missing.

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?

Schema coverage is 100%, so the schema documents both parameters fully, setting the baseline at 3. The description reinforces the 'by hash' lookup and Ethereum-only framing, which clarifies that the optional network parameter is effectively fixed to Ethereum for this tool, adding modest meaning beyond the schema.

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 resource and retrieval shape: a single Ethereum transaction by hash, including the receipt with status, gas and logs. The scope (Ethereum, one transaction) implicitly separates it from aggregate siblings like wallet_report or multichain_wallet_report, though no sibling is named.

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 – you use it when you have a transaction hash and want full details. There is no explicit when-to-use versus when-not guidance, and no mention of what to do when the hash is unknown or the transaction is pending.

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