Skip to main content
Glama

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

Optimism ERC-20 balance

op_token_balance
Read-only

ERC-20 token balance of a wallet on Optimism (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 op_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": "op_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?

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), and the description adds real context beyond them: exact return fields, the 422-on-non-ERC-20 behavior, uncharged failures, and per-call pricing with 25 free calls. It even explains why idempotentHint=false despite being a read — calls are billed, so repeats aren't free — which is a genuinely useful reconciliation of the annotation.

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?

Purpose is front-loaded in the first clause, and the remaining sentences carry distinct information (alternatives, input formats, error behavior, pricing). It is dense and semicolon-chained, with pricing details consuming meaningful space, but nothing is truly redundant.

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 correctly specifies the return shape (raw amount, decimals, symbol, human-readable amount). It also covers cost, error behavior, and immutability, so an agent has everything needed to call it and interpret the result.

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, and the description mostly restates them (tickers like USDC/USDT/WETH, 0x contract addresses). It adds the 40-hex-character address format, which is useful, but the claim that 'both inputs are 0x addresses' sits awkwardly against the token field accepting tickers.

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 Optimism), names the underlying mechanism (balanceOf), and explicitly distinguishes itself from the native-coin sibling op_balance. The chain scope plus token scope make it unambiguous which sibling to pick.

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 clause ('check stablecoin or token holdings before a transfer or trade') and an explicit when-not/alternative ('for the native coin use op_balance'). It also flags the failure case (no contract or non-ERC-20 returns 422) so the agent knows what a bad input looks like.

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.