Skip to main content
Glama

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

Ethereum ERC-20 token balance of a wallet

eth_token_balance
Read-only

Get ERC-20 token balance. ERC-20 token balance for any Ethereum wallet: balance of one token (USDC, USDT, DAI or any ERC-20 contract) for one address, with token name, symbol, decimals and total supply. Ethereum mainnet, public RPC data. Price: $0.001 USDC per call (x402 v2, Base). Free demo: https://api.zato.org/demo/eth/token-balance

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

Input Schema

NameRequiredDescriptionDefault
tokenYesERC-20 token contract
addressYesWallet address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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, and the description goes beyond them by disclosing the cost model ('$0.001 USDC per call', x402 v2 on Base), a demo endpoint, the data source (public Ethereum mainnet RPC), and the fields returned. It stops short of 5 because it omits failure modes (unknown token contract, rate limits) and whether the x402 payment is mandatory before the call succeeds.

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 opening two sentences restate each other ('Get ERC-20 token balance. ERC-20 token balance for any Ethereum wallet'), which is wasted space. The pricing, network, and demo details do earn their place but are crammed into a single trailing line rather than front-loaded after the core purpose.

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 two-parameter read tool with full schema coverage and annotations covering the safety profile, the description supplies what the structured fields do not: chain, cost, data source, and the shape of the returned token metadata. There is no output schema, but the listed return fields (name, symbol, decimals, total supply) reasonably compensate.

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 patterns already constrain both arguments to 0x-prefixed 40-hex addresses, so the schema carries the burden. The description adds only modest value: it clarifies that exactly one token and one address are queried and gives example token identifiers (USDC, USDT, DAI), but no format or edge-case detail 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?

The description states a specific verb and resource ('Get ERC-20 token balance') and pins down the chain and scope ('for any Ethereum wallet', 'one token ... for one address'), which lets an agent separate it from chain-specific siblings such as base_wallet or solana_wallet. It never explicitly names a sibling it should not be used for, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no routing to alternatives (e.g., native ETH balance versus token balance, or Base versus Ethereum). The agent must infer usage purely from the tool name and the phrase 'Ethereum mainnet, public RPC data'.

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