Skip to main content
Glama

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

Ethereum wallet balance (ETH + top ERC-20 tokens)

eth_wallet
Read-only

Ethereum wallet balance lookup: native ETH balance plus ERC-20 token balances (USDC, USDT, DAI, WETH, WBTC, LINK, UNI and up to 10 extra tokens), transaction count (nonce) and contract/wallet flag for any Ethereum mainnet address. Public RPC data, real-time. Price: $0.001 USDC per call (x402 v2, Base). Free demo: https://api.zato.org/demo/eth/wallet

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

Input Schema

NameRequiredDescriptionDefault
tokensNoOptional extra ERC-20 tokens
addressYesEthereum address
include_zeroNoAlso list tokens with zero balance

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds real value beyond that with real-time public RPC sourcing, a concrete price ($0.001 USDC per call via x402 on Base), and a free demo endpoint. It also discloses the return payload (nonce and contract/wallet flag) that no output schema provides. It stops short of describing error or rate-limit behavior.

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?

One dense front-loaded sentence covers purpose and payload, followed by short operational clauses for pricing and demo access. Every element earns its place; the parenthetical token list is the only slightly bulky part.

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, the description correctly compensates by enumerating return fields, and it also covers the payment model and token cap. For a three-parameter read-only lookup this is nearly complete, with only failure modes left unstated.

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 each of the three parameters already carries a description and pattern, so the schema does the heavy lifting. The description contributes the 'up to 10 extra tokens' cap and names the default tracked tokens (USDC, USDT, DAI, WETH, WBTC, LINK, UNI), which is modest added meaning rather than new syntax or format detail.

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 ('Ethereum wallet balance lookup') and enumerates exactly what is returned: native ETH, ERC-20 balances with a named default token set, nonce, and contract/wallet flag. It implicitly separates itself from the narrower eth_token_balance sibling by saying 'native ETH balance plus ERC-20 token balances', but it never names that sibling explicitly.

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 description — you call it when you need a full wallet snapshot for an Ethereum mainnet address — but there is no explicit when-to-use/when-not guidance and no mention of eth_token_balance for token-only queries. The pricing and free-demo URL give operational context but do not route between alternatives.

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