Skip to main content
Glama

zato crypto data

Wallet report on Ethereum or Base: ETH and ERC-20 token balances, nonce and recent transfers in one call

wallet_report
Read-only

One wallet on one chain: native + top token balances, nonce, contract flag, recent token transfers. network: ethereum (default), base, arbitrum, optimism, polygon, bnb, avalanche, linea, scroll, zksync, gnosis, celo or solana. Accepts ENS/Basenames. Price: $0.003 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": "wallet_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesWallet or contract address to report on (0x + 40 hex chars) or ENS/Basename (vitalik.eth, name.base.eth)
networkNoethereum (default), base, arbitrum, optimism, polygon, bnb, avalanche, linea, scroll, zksync, gnosis, celo or solana

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 safety profile is covered. The description adds genuinely useful non-schema behavior: per-call pricing ($0.003 USDC via x402 on Base) and ENS/Basename resolution, which an agent needs before committing a paid call. It omits any indication of how many transfers are returned or whether results are cached.

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?

The return payload is front-loaded in the first clause, followed by network options and price, so nothing critical is buried. The long network enumeration duplicates the schema and could be trimmed, but overall it is tight for the amount of information conveyed.

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 the response, and it does so at a high level. The remaining ambiguity is 'top token balances' — the count or cap on tokens and transfers is never specified — but pricing, defaults, and accepted address formats are all covered.

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 address and network are already documented, including the ENS/Basename and 0x formats. The description restates the network list and ENS support rather than adding new semantics, so it earns the baseline rather than more.

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 description names a specific verb+resource and enumerates exactly what is returned: native and top token balances, nonce, contract flag, and recent token transfers. The scoping phrase 'One wallet on one chain' cleanly distinguishes it from siblings like multichain_wallet_report and batch_wallet_report.

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?

'One wallet on one chain' gives a clear selection signal against multi-wallet or multi-chain variants, and the default network is stated. It stops short of explicitly naming an alternative tool or stating when not to use it, so it is strong context rather than full routing guidance.

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