Skip to main content
Glama

zato crypto data

USDC balance of an address on 12 EVM chains (or one) in one call

usdc_balance
Read-only

Only the USDC balance of an address, on all 12 EVM chains or one. Price: $0.001 USDC per call (x402, Base).

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": "usdc_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesaddress or ENS/Basename
networkNooptional single chain, e.g. base

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 does not need to restate safety. It adds genuinely non-obvious behavior: the call is paid, costing $0.001 USDC per call via x402 on Base, which an agent must know before invoking. It does not disclose how chains with zero balance or failed RPCs are represented in the response.

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?

Two short sentences, both front-loaded: scope first, cost second. Nothing is padded or repeated from the name, and the most decision-relevant fact for an agent (the price) is captured in a single clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 should describe the return shape, such as per-chain balance mapping and how absent chains appear; it does not. Pricing, scope, and chain behavior are covered, so it is adequate for invocation but leaves the result interpretation to inference.

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 parameters are already documented, giving a baseline of 3. The description adds one useful nuance beyond the schema: omitting the network aggregates across all 12 chains, whereas the schema only says the field is an optional single chain.

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 title and description state a specific resource (USDC balance of an address) and an explicit scope (all 12 EVM chains, or one). The word 'Only' deliberately contrasts with broader sibling tools like balance_at or multichain_wallet_report, so an agent can distinguish it 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 Guidelines4/5

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

'Only the USDC balance' clearly signals the condition for use (single-asset, multi-chain balance lookup) versus broader portfolio/report tools. It stops short of naming the alternative for other tokens or explaining when to pass a single network versus omitting it, so there is context but no explicit routing instructions.

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