Skip to main content
Glama

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

ERC-20 Transfer events for a token or wallet

eth_transfer_logs
Read-only

ERC-20 Transfer logs via eth_getLogs: recent Transfer events for a token contract, optionally filtered by a wallet (sender or receiver), decoded (from, to, amount, block, tx hash). Searches up to the last 2,000 blocks, max 100 events. Ethereum mainnet, public RPC data. Price: $0.002 USDC per call (x402 v2, Base). Free demo: https://api.zato.org/demo/eth/transfer-logs

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": {
      "token": "<token>"
    },
    "name": "eth_transfer_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
tokenYes
blocksNo
walletNoOptional: only transfers from or to this address

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly and openWorld annotations, the description discloses practical behavior: searches up to the last 2,000 blocks, caps results at 100 events, runs on Ethereum mainnet with public RPC data, and costs $0.002 USDC per call via x402 v2 on Base. It also provides a free demo URL, which is valuable context for an agent deciding whether and how to invoke it.

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?

The description is front-loaded with the core purpose and efficiently packs constraints, pricing, and a demo link into a compact paragraph. It is slightly dense with pricing and URL details, but no sentence is clearly wasteful.

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?

With no output schema, the description still explains the decoded return shape (from, to, amount, block, tx hash). It also covers network, block/event limits, and cost, giving an agent everything needed to call the tool correctly.

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 description coverage is only 25%, so the description must carry weight and largely does: it clarifies that token is a contract address, wallet filters by sender or receiver, and blocks controls the lookback window up to 2,000 blocks while limit caps events at 100. It does not explain the default values (200 blocks, 25 events), which keeps it from a 5.

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 and resource: ERC-20 Transfer logs via eth_getLogs, with optional wallet filtering and decoded output fields. An agent can distinguish this from sibling tools like eth_token_balance or eth_tx without opening the schema.

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 description implies when to use it—for recent Transfer events of a token contract, optionally narrowed to a wallet—but it never explicitly states when to choose this over alternatives such as eth_tx. No exclusions or alternative routing 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