Skip to main content
Glama

Native balance and the major tokens of an EVM address

evm_wallet
Read-only

Native balance and the major tokens (USDC, USDT, EURC, DAI, WETH, cbBTC and WBTC where listed) of an EVM address on Base (default), Ethereum, Arbitrum, Optimism, Polygon, or chain=all, with USD values from Coinbase spot prices. One Multicall3 call per chain. Zero balances are omitted, and only the listed tokens are checked, not every token the wallet holds. Related tools on this server, for a different need: evm_address when you need native balance, nonce and account type of an EVM address; evm_balance when you need ERC-20 balance of an address for one token contract. Price: $0.003 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls 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": "evm_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNobase (default), ethereum, arbitrum, optimism, polygon or all
addressYesWallet address, 0x…

Output Schema

NameRequiredDescriptionDefault
notesNo
chainsNo
addressNo
sourcesNo
totalUsdNo
checkedAtNo
disclaimerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "address": {},
      +    "chains": {},
      +    "checkedAt": {},
      +    "disclaimer": {},
      +    "notes": {},
      +    "sources": {},
      +    "totalUsd": {}
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say readOnly/openWorld, but the description goes further: one Multicall3 call per chain, zero balances omitted, only the seven listed tokens are checked (explicit scope limitation), USD values come from Coinbase spot prices, and pricing/charging behavior ($0.003 per successful call via x402, failures not charged). These are material behaviors an agent could not infer from structured fields.

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 core capability, the token-list caveat, and the sibling routing are front-loaded in a logical order with no filler. It is dense — three distinct concerns (behavior, alternatives, billing) packed into one block — but each sentence carries information an agent needs.

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?

An output schema exists, so return-value structure need not be explained; the description still covers the interpretation-critical parts (zero balances dropped, non-listed tokens absent, USD pricing source). For a two-parameter read tool this leaves no operational gap.

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% and already documents chain and address, so the baseline is 3. The description adds real meaning on top: what chain=all actually does (queries every supported chain), that Base is the default, and that the token set is fixed rather than exhaustive — which reframes how to interpret results.

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 specific resource (native balance plus a named set of major tokens) scoped to an EVM address across named chains, and explicitly separates it from evm_address (native balance/nonce) and evm_balance (single ERC-20 contract). An agent can distinguish all three 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names both alternative tools and the exact condition that selects each ('when you need native balance, nonce and account type' vs 'when you need ERC-20 balance ... for one token contract'). It also states the default chain (Base) and the chain=all option, so when-to-use is fully resolved.

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