Skip to main content
Glama

x420_chain_wallet-balance

Fetch an address's ETH, USDC, and any named ERC-20 balance on Base mainnet at the current block via public RPC in one paid call.

Instructions

Base wallet balance: ETH and USDC balance of an address on Base mainnet at the current block, plus any one ERC-20 you name, read through the public RPC (free, no key). Source: Base mainnet RPC. Not professional, legal, insurance, engineering, medical, financial or tax advice. PAID: $0.02 USDC per call, settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY (real money). Returns: JSON: block, eth{wei, ether}, usdc{atomic, amount}, token{symbol, amount} - the deliverable plus X420's signed receipt and the settlement transaction. Example input: {"address":"0x4200000000000000000000000000000000000006"}.

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": "x420_chain_wallet-balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenNooptional ERC-20 contract address to include (default: none)
addressYes0x wallet address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations, it discloses that each call costs $0.02 USDC of real money, is settled on Base via x402 from a specific private key, and returns a signed receipt plus the settlement transaction. That is material behavioral context an agent must know before invoking. One wrinkle: it calls the public RPC 'free, no key' while also charging per call, which reads as internally inconsistent, though it does not contradict the readOnlyHint=false annotation (payment spending explains the write-flagged profile).

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 core scope is front-loaded and the return fields are clearly enumerated, but the body is a dense multi-clause run-on that mixes pricing, settlement, disclaimers, and return shape in one block. The legal disclaimer sentence is boilerplate that dilutes the operational content.

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?

There is no output schema, so the description compensates by enumerating the returned JSON fields (block, eth, usdc, token) plus receipt and settlement transaction. Cost, payment path, and data source are all covered, leaving little an agent needs that is missing for a two-parameter read tool.

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 coverage is 100%, so both parameters are documented in the schema. The description adds one useful nuance, that the token parameter is limited to 'any one ERC-20 you name', plus a concrete example input. That is a modest addition over the schema's 'optional ERC-20 contract address'.

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?

States a specific verb and resource: it reads ETH, USDC, and one optional ERC-20 balance for an address on Base mainnet at the current block. That is far more specific than the name alone. It does not explicitly distinguish itself from siblings such as token-metadata or gas-estimate, though the resource distinction is implicit.

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?

The description implies when the tool applies (balance lookup at current block) and notes the data source, but it gives no when-not-to-use guidance and names no alternative for related queries like token metadata or gas estimation. Usage is inferable rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.