Skip to main content
Glama

zato crypto data

Batch wallet report: up to 20 addresses or ENS names on one chain in one call

batch_wallet_report
Read-only

Up to 20 wallets (addresses or ENS names) on one chain in one call, for screening lists. Price: $0.03 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": {
      "addresses": "<addresses>"
    },
    "name": "batch_wallet_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNoethereum (default), base, arbitrum, optimism, polygon, bnb, avalanche, linea, scroll, zksync, gnosis or celo
addressesYescomma-separated addresses or ENS/Basenames, max 20

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/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's real addition is commercial behavior: $0.03 USDC per call via x402 on Base, which is context the annotations cannot express and matters for agent budgeting. It still omits what the returned report contains and whether unresolvable addresses fail the whole batch.

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?

Two short sentences, the capacity and chain constraint front-loaded, price trailing. Nothing is redundant within the description, though the title nearly duplicates the body word for word.

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?

There is no output schema, so the description bears the burden of saying what a wallet report yields, and "for screening lists" is the only hint. Payment terms and the batch limit are covered, but an agent cannot tell what signals, labels or verdicts come back or how partial failures are handled.

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 the schema already documents both parameters, the network list and the max-20 constraint. The description repeats the limit and the ENS support without adding syntax or format detail beyond the schema, so baseline 3 applies.

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 concrete verb-and-resource pair: a batch wallet report over up to 20 addresses or ENS names, constrained to a single chain. The phrase "one chain in one call" implicitly separates it from the single-wallet and multichain siblings, but no sibling is actually named, so differentiation is only partially explicit.

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?

"for screening lists" gives a usage context, and "on one chain" hints that multi-chain work belongs elsewhere, but the tool never states when to choose it over wallet_report, multichain_wallet_report or sanctions_check. The guidance is implied rather than stated.

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