Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Arbitrum One ERC-20 balance

arb_token_balance
Read-only

ERC-20 token balance of a wallet on Arbitrum One (USDC, USDT, WETH or any token, via balanceOf): raw amount, decimals, symbol and the human-readable amount, live from the token contract. Use to check stablecoin or token holdings before a transfer or trade; for the native coin use arb_balance. Both inputs are 0x addresses (40 hex characters); no contract or a non-ERC-20 contract returns 422, uncharged. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": {
      "token": "<token>",
      "address": "<address>"
    },
    "name": "arb_token_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesToken: a ticker such as USDC, USDT, WETH or DAI, or the 0x ERC-20 contract address
addressYes0x wallet address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations (readOnly, non-destructive, openWorld), it discloses failure semantics (missing or non-ERC-20 contract returns 422 and is uncharged) and the pricing/rate model ($0.01/call, first 25 free, failed calls free). It also clarifies why repeated identical calls are not free, which usefully explains the idempotentHint=false annotation rather than contradicting it. The only minor gap is no hint about latency or caching of the live contract read.

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?

Front-loaded with the core purpose and return fields, then usage routing, then constraints and pricing. Dense but mostly earning its space; the pricing/free-call clause is the least essential part and makes the sentence run long.

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

Completeness5/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 carries the return-shape burden and does so explicitly (raw amount, decimals, symbol, human-readable amount). Combined with error semantics, the alternative-tool pointer and cost model, an agent has everything needed to call it correctly.

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 the schema already documents both parameters and the baseline is 3. The description adds address format (40 hex characters) and error behavior for a bad token, but the claim that 'both inputs are 0x addresses' sits awkwardly against the schema's statement that token may be a ticker such as USDC — a small inconsistency that undercuts the added clarity.

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 ('ERC-20 token balance of a wallet on Arbitrum One'), names the underlying method (balanceOf) and enumerates the returned fields. It explicitly separates itself from the native-coin sibling arb_balance, so an agent can route between them without opening a schema.

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

Usage Guidelines5/5

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

Gives an explicit use case ('check stablecoin or token holdings before a transfer or trade') and an explicit alternative with the condition that selects it ('for the native coin use arb_balance'). Little is left to inference about when this tool is the right choice.

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.