Skip to main content
Glama

APEX DeFi, DefiLlama & 8-Chain EVM Intel

Evm balances bulk

evm_balances_bulk
Read-onlyIdempotent

Bulk wallet balances across 8 EVM chains (Ethereum, Base, Arbitrum, Optimism, Polygon, BNB Chain, Arc and Robinhood): up to 50 wallets in one call, native coin or one ERC20, read at one block via Multicall3. $0.005 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
chainNoethereum (default), base, arbitrum, optimism, polygon, bnb, arc or robinhood
tokenNooptional ERC20 (0x...)
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.
addressesYesup to 50 wallet addresses, comma-separated

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover the read-only/idempotent/non-destructive profile, so the description adds genuinely new behavioral facts: a per-call price ($0.005), the accepted payment assets and chains, the mandatory two-call payment handshake, and the Multicall3 atomic single-block read. These are things an agent cannot infer from annotations and materially affect how it plans the call.

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?

Three dense sentences, front-loaded with the core capability, then limits, then pricing/payment mechanics. No filler, though the long parenthetical chain roster and the payment-asset enumeration make the middle heavy; a compact chain list would read faster.

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?

For a paid, multi-chain read tool this covers purpose, limits, payment handshake and read semantics, which is most of what an agent needs. The notable gap is the absence of an output schema combined with no description of the returned balance shape (symbols, decimals, per-wallet ordering) or error behavior when more than 50 addresses are supplied.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: it enumerates the valid chain set, clarifies that `token` allows only one ERC20 at a time (defaulting to the native coin), and frames `payment` as the signed payload that completes the purchase inline. The per-parameter ceiling of 50 addresses is also restated in prose context.

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 precise verb+resource (bulk wallet balances) plus scope: 8 named chains, up to 50 wallets, native coin or a single ERC20, all read at one block via Multicall3. That combination makes it clearly distinguishable from single-wallet siblings like evm_wallet_balance or evm_token_balance without opening their schemas.

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?

The description gives explicit operational guidance for the two-step x402 flow: call first without `payment` to obtain terms, sign with your own wallet, call again with `payment`. It also implies when bulk is appropriate via the 50-wallet limit. It stops short of explicitly naming a sibling for the single-wallet case or stating when-not to use bulk (e.g. one address).

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.