Skip to main content
Glama

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

Batch balance check for up to 25 Base addresses

base_wallets
Read-only

Batch wallet balance lookup on Base. ETH balance, USDC balance, transaction count and contract/wallet flag for up to 25 Base (eip155:8453) addresses in one call. Public on-chain data only. Price: $0.003 USDC per call (x402 v2, Base). Free demo: https://api.zato.org/demo/base/wallets

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": {
      "addresses": "<addresses>"
    },
    "name": "base_wallets"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 the description earns credit for adding non-obvious behavior: a paid endpoint at $0.003 USDC per call via x402 v2 on Base, a free demo URL, and the 25-address cap. It does not state what happens on invalid addresses or whether failed/batched lookups are still billed, which keeps it from a 5.

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?

Three tight sentences plus a demo URL; the operation and its scope are front-loaded, followed by return fields, then cost/payment. Every sentence carries distinct information with no repetition of the name or title.

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 fills the gap by listing the returned fields, and it covers cost, payment rail, and input limits. Remaining gaps are error/partial-failure behavior and result ordering relative to the input array, which an agent would need to handle results 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?

Only one parameter, and the schema itself carries the constraints (regex pattern, minItems 1, maxItems 25). The description reinforces the limit and clarifies that addresses are Base/eip155:8453, adding chain semantics the schema does not encode. Little more is needed for a single address-list parameter.

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 opens with a specific verb and resource ("Batch wallet balance lookup on Base") and enumerates exactly what is returned: ETH balance, USDC balance, transaction count, and contract/wallet flag. The 25-address scope and chain identifier (eip155:8453) further pin it down. It does not explicitly name base_wallet as the single-address alternative, so it stops 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 Guidelines3/5

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

Usage is implied by "Batch... for up to 25 addresses in one call" and "Public on-chain data only," which signals when this is the right tool. However, there is no explicit when-not guidance and no named alternative for single-address lookups even though base_wallet exists in the sibling set.

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