Skip to main content
Glama

AgentIndex x402

by world.agentindex
OverviewDiscussionsAdmin

Wallet Balance

wallet_balance
Read-onlyIdempotent

Read native coin and USDC balances for any EVM wallet on Base, Ethereum, Polygon, Arbitrum or Optimism, with atomic amounts and current block. No RPC key or account. Try GET /wallet-balance/sample.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesEVM wallet address (0x followed by 40 hexadecimal characters).
networkNoEVM network to read; aliases and CAIP-2 identifiers are also accepted.base

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
usdcYes
nativeYes
addressYes
networkYes
block_numberYes
x402_receiptNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / address / description
      Added value: +"EVM wallet address (0x followed by 40 hexadecimal characters)."
    • addedInput schema / properties / network / description
      Added value: +"EVM network to read; aliases and CAIP-2 identifiers are also accepted."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "address": {
+      "type": "string"
+    },
+    "block_number": {
+      "type": "integer"
+    },
+    "native": {
+      "type": "object"
+    },
+    "network": {
+      "type": "object"
+    },
+    "usdc": {
+      "type": "object"
+    },
+    "x402_receipt": {
+      "type": "object"
+    }
+  },
+  "required": [
+    "address",
+    "network",
+    "block_number",
+    "native",
+    "usdc"
+  ],
+  "type": "object"
+}
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint, so the safety profile is covered. The description adds real context beyond that: no RPC key or account required, response contains atomic amounts plus current block, and the supported chain set. Rate limits and failure behavior remain undisclosed.

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 tightly packed sentences front-load the operation and scope, with no filler. The trailing 'Try GET /wallet-balance/sample' is short but cryptic in this context, slightly dulling an otherwise clean structure.

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?

An output schema exists, so return-value explanation is unnecessary, and annotations carry the safety profile. The description still covers chains, auth-free operation, and amount format, leaving only rate-limit and error semantics unstated for a simple read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and only two params exist, but the schema's network field never enumerates the supported networks, having no enum. The description supplies that missing value list (Base, Ethereum, Polygon, Arbitrum, Optimism), which is genuine added meaning for the network parameter.

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 gives a specific verb and resource: 'Read native coin and USDC balances for any EVM wallet', and enumerates the five supported chains, so the agent knows exactly what data comes back. It does not explicitly contrast itself with nearby siblings such as wallet_intelligence or gas_price, leaving differentiation to inference.

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?

Usage is implied by the scope ('read balances on these chains'), and 'No RPC key or account' quietly signals the no-setup condition. However, there is no statement of when to prefer this over wallet_intelligence or gas_price, and no exclusions or prerequisites spelled out.

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

All AgentIndex x402 toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources