Skip to main content
Glama

ERC-20 balance (x402)

get_chain_erc20_balance

Read-onlyIdempotent

Any wallet's balance of any ERC-20 token (USDC, USDT, DAI, or any contract) via balanceOf, across Base, Ethereum, Optimism, Arbitrum, Polygon, Gnosis. The token-balance read wallet-tracking, copy-trade, treasury and trading agents poll constantly — the most-called RPC read after native balance. Live public RPC; 6 chains vs onesource's Ethereum-only coverage.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_chain_erc20_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
x_paymentNoSigned x402 payment payload

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, open-world semantics, so the safety profile is covered. The description adds real value with the six-chain list and 'Live public RPC', but says nothing about rate limits, reliability, or what happens when a token/wallet is unknown — despite 'Live public RPC' hinting at shared, potentially throttled infrastructure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is well front-loaded and information-dense. The trailing sentence ('the most-called RPC read after native balance ... vs onesource's Ethereum-only coverage') is marketing filler that spends words on a competitor comparison rather than on operational detail.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool claiming 'any wallet's balance of any ERC-20 token ... across six chains', the definition never explains how the agent specifies wallet, token contract, or chain, nor what the returned value looks like (raw units vs decimals) with no output schema to fall back on. The missing input-to-parameter mapping is a substantial gap for a call the description itself says is polled constantly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% but the single exposed parameter (x_payment, a signed x402 payload) is never mentioned in the description, so the agent gets no hint that payment is required. Worse, the description implies wallet, token, and chain inputs that the schema does not expose at all, leaving unclear where those values are supplied.

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?

Names a specific verb and resource ('balance of any ERC-20 token ... via balanceOf') and enumerates the token standards/chains covered. It implicitly distinguishes itself from the native-balance sibling by calling itself 'the most-called RPC read after native balance', though it never names that sibling directly.

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?

Usage is implied through the audience list ('wallet-tracking, copy-trade, treasury and trading agents') and the ERC-20-vs-native framing, but there are no explicit when-to-use/when-not rules and no named alternative for native balances or allowances.

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