Skip to main content
Glama

Native balance (x402)

chain_native_balance

Read-onlyIdempotent

$0.003 via x402: the core on-chain RPC read — any address's native coin balance (ETH/POL/xDAI) with live USD value and outgoing transaction count, across Base, Ethereum, Optimism, Arbitrum, Polygon, Gnosis. The high-frequency balance check wallet-tracking, settlement and trading agents poll constantly. Live from Blockscout; 6 chains vs onesource's Ethereum-only.

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": "chain_native_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNobase|ethereum|optimism|arbitrum|polygon|gnosis (default base)
addressYesAccount address (0x...)
x_paymentNox402 payment payload (base64) to settle this call; omit to receive the payment terms first

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly/idempotent/openWorld, and the description usefully adds the data source (Blockscout), live pricing ($0.003 via x402) and the payment handshake implied by x_payment. It does not describe freshness/latency, rate limits, or failure modes for an unpaid call, so it adds real but partial behavioral context.

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 capability and chain list are front-loaded and the price is stated up front, which is efficient. However, promotional phrasing ('the high-frequency balance check... agents poll constantly', 'vs onesource's Ethereum-only') is marketing padding that does not help an agent call the tool correctly.

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 does name the return contents (native balance, live USD value, outgoing tx count) and the data source, which is the key missing piece for an agent. It still omits return formatting/units and payment-failure behavior, but it is otherwise sufficient for a single required address plus optional chain.

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 100%, so the schema already documents the chain enum, address format, and x_payment purpose. The description reinforces chain coverage and the returned metrics but adds no new meaning about parameter syntax or defaults beyond what the schema states.

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?

States a specific verb+resource: reads any address's native coin balance (ETH/POL/xDAI) with live USD value and outgoing transaction count across six named chains. It also implicitly distinguishes itself from the ERC20 sibling by naming 'native coin' and from 'onesource' by chain coverage, so an agent can select it without opening schemas.

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

Usage Guidelines4/5

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

Gives clear usage context — wallet-tracking, settlement and trading agents polling balance — and contrasts chain coverage against an alternative (onesource's Ethereum-only). It stops short of explicit when-not guidance or naming any sibling tool directly, so it lands at clear-context-without-exclusions rather than a full routing rule.

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