Skip to main content
Glama

APEX DeFi, DefiLlama & 8-Chain EVM Intel

Evm wallet balance

evm_wallet_balance
Read-onlyIdempotent

Wallet balance across 8 EVM chains (Ethereum, Base, Arbitrum, Optimism, Polygon, BNB Chain, Arc and Robinhood): native coin (ETH, POL, BNB, or USDC on Arc), the chain USDC or up to 20 ERC20 tokens you list, nonce, and whether the address is a contract. $0.002 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": {
      "address": "<address>"
    },
    "name": "evm_wallet_balance"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower, and the description still adds genuinely non-obvious behavior: a $0.002 per-call price, the accepted settlement assets, and a required two-step x402 handshake. It omits failure modes (what happens with an invalid or underpaid payment payload) and rate limits.

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?

Three sentences, no filler, with the highest-value facts (chains and payload) front-loaded and the payment protocol trailing as a procedural note. The parenthetical lists are dense but each element is load-bearing.

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 read-only 4-parameter tool with no output schema, the description covers scope, cost, settlement, and the payment lifecycle adequately. The main residual gap is that it never states the response shape (per-chain grouping, units, decimals) despite having no output schema to lean on.

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 real meaning on top: which native coin each chain yields (ETH, POL, BNB, USDC on Arc), the default chain behavior, the 20-token cap on `tokens`, and — most importantly — that `payment` must be produced by signing previously returned terms. That last point clarifies the lifecycle of the trickiest parameter.

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 names a specific verb+resource (wallet balance) and enumerates exactly what is returned: native coin, chain USDC or up to 20 ERC20 tokens, nonce, and contract status across eight named chains. It does not explicitly differentiate itself from siblings such as evm_token_balance or evm_balances_bulk, leaving that routing to inference.

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?

Strong procedural guidance is given for the paid flow: 'Call once without payment for the terms, sign them with your own wallet, call again with payment.' However, there is no guidance on when to pick this over evm_balances_bulk (multi-wallet) or evm_token_balance (single token), which is the core of this dimension.

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.