Skip to main content
Glama

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

Latest Ethereum block height and header

eth_block
Read-only

Latest Ethereum block height (current chain tip) via eth_blockNumber, plus the block header: timestamp, age in seconds, base fee (gwei), gas used/limit and transaction count. Optional block number. Ethereum mainnet, public RPC data. Price: $0.0005 USDC per call (x402 v2, Base). Free demo: https://api.zato.org/demo/eth/block

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "eth_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
blockNoOptional block number (default: latest)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish readOnlyHint and openWorldHint, so the safety profile is covered. The description contributes real context beyond that: the upstream RPC method, mainnet-only data source, a per-call price of $0.0005 USDC via x402 v2 on Base, and a free demo endpoint — payment and provenance details an agent cannot get from structured fields.

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?

Front-loaded with the core purpose and the returned fields in a single dense sentence, then scope and pricing. No filler or repetition; every clause carries information an agent would need.

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 one-optional-parameter read tool with no output schema, the description fully specifies inputs, the shape of returned data, data source, and cost. An agent could select and invoke this correctly without further information.

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 single `block` parameter is already documented there, including the '(default: latest)' semantics. The description restates the same 'Optional block number' information without adding format, range, or archive-depth guidance, so baseline 3 applies.

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?

Names a specific verb and resource — 'Latest Ethereum block height (current chain tip) via eth_blockNumber' — and enumerates the returned header fields (timestamp, base fee, gas used/limit, tx count). That clearly separates it from siblings like eth_tx or eth_contract, which target transactions and contracts rather than block headers.

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?

The 'Optional block number (default: latest)' note implies that omitting the parameter yields the chain tip, which gives implicit usage guidance. However, there is no explicit when-to-use framing against alternatives (e.g., use eth_tx for a specific transaction) and no note on whether historical blocks require archive access.

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