Skip to main content
Glama

X420 agent services

x420_chain_wallet-balance

Read-onlyIdempotent

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. Price: $0.02 USDC per call (x402 on Base). This hosted tool does NOT pay and does NOT return the deliverable: it validates the input and returns payment instructions (pay_to, network, price and the x402 URL to pay at). GET the url; read PAYMENT-REQUIRED from the 402; retry with PAYMENT-SIGNATURE (x402 v2). Or run the local x420-mcp server with your own wallet key to pay automatically. Deliverable once paid: JSON: block, eth{wei, ether}, usdc{atomic, amount}, token{symbol, amount}.

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 observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds far more: the tool does NOT return the deliverable, it validates input and returns payment instructions (pay_to, network, price, x402 URL), the exact 402/PAYMENT-SIGNATURE retry protocol, and the $0.02 USDC cost. That is precisely the behavior an agent needs before calling.

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?

Purpose is correctly front-loaded, but the block is bloated: a generic 'not professional, legal, insurance... advice' disclaimer earns nothing for tool selection, and the payment protocol walkthrough is dense prose where a shorter sequence would serve. Roughly a third of the text is non-operative boilerplate.

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?

With no output schema, the description compensates by specifying the paid deliverable shape (block, eth{wei,ether}, usdc{atomic,amount}, token{symbol,amount}). Combined with the payment instructions, an agent knows the full lifecycle. Minor gaps remain, e.g. behavior on invalid address or RPC failure.

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 already documented. The description adds only that the token parameter is 'any one ERC-20 you name' and that the balance snapshot is 'at the current block' — marginal value beyond the schema, so baseline 3 applies.

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?

Names a specific resource and scope: 'ETH and USDC balance of an address on Base mainnet at the current block, plus any one ERC-20 you name.' That verb+resource+scope combination distinguishes it from siblings like x420_chain_token-metadata without needing to open their schemas.

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?

Explains the operational flow (this hosted tool returns payment instructions; pay via x402 or use the local x420-mcp server with your own key), but never says when to pick this over a sibling such as token-metadata, nor any explicit exclusions. Usage is implied by the stated scope rather than guided.

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