Skip to main content
Glama

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

Ethereum ERC-20 balance

eth_token_balance
Read-only

ERC-20 token balance of a wallet on Ethereum (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 eth_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": "eth_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.2/5.0
Behavior3/5

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

Beyond the annotations it discloses error behavior (422 on non-ERC-20 contracts, uncharged), pricing ($0.01/call via x402 or card key, first 25 free, failed calls free) and the returned fields, which explains the otherwise puzzling idempotentHint=false as a cost-per-call rather than a state-change issue. It is thorough, but the annotations already carry the read-only/non-destructive/open-world profile, so the added value is pricing and error semantics rather than core behavior.

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 paragraph, correctly front-loaded with purpose, then usage, then parameter format, then pricing/error notes. Every sentence carries information, though the pricing and free-tier clause could be tightened and the parameter-format sentence is both long and inaccurate.

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 compensates by naming the return fields (raw amount, decimals, symbol, human-readable amount) and noting the data is live from the contract. Error semantics, payment/auth options and cost behavior are all covered for a two-parameter read tool.

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 baseline is 3 and the description mostly restates the schema. It does add format guidance, but that guidance is partly wrong: 'Both inputs are 0x addresses (40 hex characters)' conflicts with the schema, which allows the token parameter to be a ticker such as USDC or DAI. An agent reading only the description could wrongly assume tickers are rejected.

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 and resource ('ERC-20 token balance of a wallet on Ethereum ... via balanceOf') and explicitly scopes it against the native-coin sibling ('for the native coin use eth_balance'). The parenthetical listing USDC/USDT/WETH/'any token' makes the resource class unambiguous.

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 when-to-use ('before a transfer or trade'), an explicit when-not with the correct alternative ('for the native coin use eth_balance'), and the edge-case routing rule that a non-ERC-20 contract returns 422. Nothing about tool selection is left to inference.

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.