Skip to main content
Glama

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

Base ERC-20 balance

base_token_balance
Read-only

ERC-20 token balance of a wallet on Base (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 base_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": "base_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.8/5.0
Behavior5/5

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

Annotations cover readOnly, destructive and openWorld, but the description adds genuinely new behavioral facts: 422 error behavior for missing/non-ERC-20 contracts, that failures are not charged, per-call pricing ($0.01 via x402 or card key), the first-25-free tier, and that repeats are not free despite being a read. The 'changes nothing' statement is consistent with readOnlyHint.

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 purpose, then usage, then error/pricing details in a single dense paragraph with no filler. Slight redundancy in restating that each call is charged after already giving the per-call price and free tier.

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?

No output schema exists, and the description compensates by naming the returned fields. Combined with error semantics, pricing, and the native-coin alternative, an agent has everything needed to call this correctly and predict the outcome.

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%, so the ticker-or-contract-address distinction for token is already documented. The description still adds validation detail beyond the schema by specifying that both inputs are 0x addresses of 40 hex characters, which the schema's '0x wallet address' omits.

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 Base') and enumerates the returned fields (raw amount, decimals, symbol, human-readable amount), so an agent knows exactly what it gets. It explicitly contrasts with the sibling base_balance for the native coin, making selection 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 a concrete use case ('check stablecoin or token holdings before a transfer or trade') and an explicit alternative for the native coin ('use base_balance'), plus failure guidance: no contract or non-ERC-20 contract returns 422 uncharged. Nothing is left to inference about when to pick this tool.

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.