Skip to main content
Glama

edge-signals

wallet_balances

Live wallet on Base: native ETH, USDC balanceOf, and nonce (optional Ethereum when configured).

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
addressYesWallet 0x

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 must carry behavioral weight. It does disclose that values are 'Live' (not cached), that the scope is the Base chain, and that Ethereum support is conditional on configuration. It omits whether the operation is read-only, what happens for an invalid or empty wallet, whether nonce is pending or confirmed, and how failures surface.

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?

A single dense sentence that front-loads the chain and asset scope with no filler. The trailing parenthetical '(optional Ethereum when configured)' is compressed to the point of ambiguity, slightly hurting readability but not wasting words.

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 one-parameter read tool with no output schema, the description covers the main return constituents but leaves the shape of results undefined (units, decimals, USD conversion, error behavior). It is minimally sufficient but leaves notable gaps for an agent deciding how to consume the output.

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% with a single required 'address' parameter described as 'Wallet 0x'. The description adds no format, checksum, or chain-compatibility detail for the address, so the schema does the work and the baseline 3 applies.

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 resource and contents: live wallet state on Base with native ETH, USDC balanceOf, and nonce. An agent knows exactly which data points come back. It does not, however, distinguish itself from siblings like wallet_nonce or erc20_balance, which overlap on the nonce and USDC concepts it names.

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 when-to-use guidance and no mention of alternatives, despite sibling tools (wallet_nonce, erc20_balance, wallet_full_bundle) covering much of the same ground. The only usage-adjacent hint is 'optional Ethereum when configured', which implies a configuration prerequisite without explaining it.

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