Skip to main content
Glama

wallet_balances

USDC + gas balances of an EVM address on Base, Ethereum, Arbitrum, Optimism, Polygon. $0.01 USDC on Base (x402).

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
addressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the disclosure burden, and it does add valuable context: the cost is $0.01 USDC paid via x402 on Base, and results cover both USDC and gas across five chains. It does not explain what happens on chains without balances, whether all chains are queried per call, or how the payment is authorized, which matters for a paid tool.

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?

Two short sentences with no filler, and the resource plus scope are front-loaded. The telegraphic, fragment-style phrasing ('USDC + gas balances of...') is efficient but slightly terse for a first-read understanding.

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

Completeness3/5

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

For a simple one-parameter tool with no output schema, the description covers the chains and the pricing model, which is most of what a caller needs. It stops short of describing the response shape or defining 'gas balances' (e.g., native token per chain), leaving real ambiguity about what a successful call returns.

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 0% for the single parameter, so the description must compensate. It partially does by clarifying the address is an 'EVM address' (implying 0x-hex format), but it gives no format example, no casing or checksum notes, and no statement about rejected address types.

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 the specific resource and verb scope well: 'USDC + gas balances of an EVM address' enumerates the five supported chains (Base, Ethereum, Arbitrum, Optimism, Polygon). That chain list clearly distinguishes it from siblings like eth_price or fetch_page, though the phrasing is a noun fragment rather than an explicit verb.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named. A caller must infer that this is the tool for balance lookups rather than price data, and nothing states prerequisites such as how the x402 payment is settled.

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