Skip to main content
Glama

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

Quick check of a Base address

base_wallet
Read-only

Base wallet balance lookup. Public on-chain snapshot of a Base (eip155:8453) address: ETH and USDC balance, transaction count, contract or wallet, plus name/symbol/decimals/supply/balance for up to 5 ERC-20 tokens. Price: $0.001 USDC per call (x402 v2, Base). Free demo: https://api.zato.org/demo/base/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": "base_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokensNoOptional ERC-20 token contracts
addressYesBase address to inspect

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 and openWorldHint, so the description's key addition is the paid-call model: $0.001 USDC per call via x402 v2 on Base, plus a free demo URL. That is material behavioral context an agent needs before invoking a metered, on-chain endpoint. It stops short of describing failure modes (unfunded x402 payment, invalid address) or freshness/latency of the snapshot.

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?

A single dense, front-loaded sentence puts the resource and return set first, with pricing and demo URL trailing. Every clause carries information, though the token-metadata enumeration is long and could be compressed since the output schema is absent but the field list is exhaustive.

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 carries the burden of describing return values and does so thoroughly (balances, tx count, account type, per-token name/symbol/decimals/supply/balance). It also covers cost and a demo path. What is missing is edge behavior: what happens when a requested token is not an ERC-20, or when the payment is not settled.

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 description coverage is 100%, so both the address and tokens parameters are already documented structurally. The description only echoes the meaningful constraints (up to 5 ERC-20 contracts alongside the address) and clarifies what per-token data comes back; it adds no format or semantics beyond the schema baseline.

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?

States a specific verb and resource ("Base wallet balance lookup") and enumerates exactly what the snapshot returns: ETH and USDC balances, transaction count, contract/wallet classification, and ERC-20 metadata. The chain identifier (eip155:8453) makes the split from the sibling eth_wallet unambiguous without opening either 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 title's "Quick check" framing and the listed outputs imply a read-only inspection use case, but there is no explicit when-to-use or when-not guidance, and no sibling (e.g. eth_wallet, base_contract, base_tx) is named as an alternative for related queries. The pricing line tells the agent about cost but not about selection.

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