Skip to main content
Glama

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

Ethereum transaction count (nonce) of an address

eth_nonce
Read-only

Ethereum address transaction count (nonce). Ethereum transaction count (nonce) for an address via eth_getTransactionCount at the latest block, plus whether the address is a contract or a wallet. Useful before building a transaction. Ethereum mainnet, public RPC data. Price: $0.001 USDC per call (x402 v2, Base). Free demo: https://api.zato.org/demo/eth/nonce

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": {
      "address": "<address>"
    },
    "name": "eth_nonce"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesEthereum address

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only say readOnly and openWorld; the description adds real context beyond them: the underlying call is eth_getTransactionCount, the block tag is 'latest', the data is public mainnet RPC, and each call costs $0.001 USDC via x402 on Base. That pricing and data-source disclosure is information 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.

Conciseness3/5

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

The first two clauses say the same thing ('Ethereum address transaction count (nonce)' then restating it), and the pricing/demo URL tail is boilerplate attached to the end. Front-loading is reasonable but a full sentence is wasted on redundancy.

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 covers chain, block tag, both returned values (nonce and contract/wallet flag), and cost. An agent knows enough to call it and interpret the result; only edge cases (pending transactions, zero-value addresses) go unmentioned.

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 coverage is 100% and the single address parameter is fully documented in the schema, so the description adds no format, casing, or normalization guidance. Baseline 3 applies when the schema does the heavy lifting.

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 concrete verb+resource: transaction count (nonce) for an Ethereum address, and adds a secondary output (contract vs wallet). The repeated opening clause duplicates the title rather than sharpening the distinction from siblings like eth_tx or eth_contract.

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 phrase 'Useful before building a transaction' gives one implied use case, but there is no explicit when-not guidance and no named alternative for reading transaction details (eth_tx) or contract status (eth_contract). Usage must be inferred.

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