Skip to main content
Glama

Multi-chain wallet balances in USD (curated tokens)

wallet_balances
Read-only

Balances of an EVM wallet (0x address, ENS name or Basename) on Base, Ethereum, Arbitrum, OP Mainnet, Polygon and Avalanche: native coin plus a curated list of 9-13 major tokens per chain (USDC, USDT, DAI, WETH, WBTC/cbBTC, AERO, ARB, OP and more), USD values, per-chain and total USD, chains holding funds, and native USDC per chain for x402 payments. Sources: each chain's JSON-RPC via PublicNode; prices from on-chain Uniswap v3 and Velodrome pools. Price: $0.003 per successful call, paid in USDC with x402 v2; failed calls and calls that match nothing are not charged.

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_balances"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainsNoComma-separated chains by name or chain id: base (8453), ethereum (1), arbitrum (42161), optimism (10), polygon (137), avalanche (43114). Default: all six.
addressYesWallet as a 0x EVM address, or an ASCII ENS name (vitalik.eth) or Basename (jesse.base.eth) resolved to its ETH address record.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses cost ($0.003 per successful call, paid in USDC via x402 v2), that failed or empty-match calls are free, the data sources (PublicNode JSON-RPC, Uniswap v3 and Velodrome pool prices), and the key limitation that token coverage is a curated 9-13 per chain rather than a full scan. This is exactly the pricing and coverage context an agent cannot get from annotations.

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 paragraph, front-loaded with what is returned, followed by sources and pricing. Every clause carries information, though the run-on enumeration of chains and tokens is slightly harder to scan than a short bulleted structure would be.

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

Completeness5/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 carries the burden of describing return values – and it does: per-token balances, USD values, per-chain and total USD totals, chains holding funds, and native USDC per chain. Combined with cost and source disclosure, an agent has everything needed to decide and call correctly.

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% and both parameters are fully documented in the schema, so the baseline is 3. The description restates that address may be a 0x address, ENS name or Basename and that coverage spans six chains, but adds no syntax or constraint detail beyond what the schema already gives (e.g. comma-separated chains and their IDs).

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 opens with a precise verb+resource ('Balances of an EVM wallet') and immediately bounds scope: six named EVM chains, native coin plus a curated 9-13 tokens per chain, USD denominated. An agent can distinguish this from token_price (single-token pricing) or ens_resolve (name resolution) without opening any 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?

Usage context is clear: multi-chain portfolio balance lookup with USD valuation, including a note that per-chain native USDC is returned for x402 payments. It does not, however, state exclusions or point at siblings such as ens_resolve for pure name-to-address lookups or token_price for arbitrary tokens.

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