Skip to main content
Glama

Money Reactor — 87 paid x402 APIs via MCP

get_erc20_balance

Paid $0.02 (x402, USDC Base): on-chain ERC20 token balance for any Base address via eth_call balanceOf on public Base RPC. Returns raw + human balance, decimals, symbol.

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": {
      "contract": "<contract>",
      "address": "<address>"
    },
    "name": "get_erc20_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesWallet address 0x...
contractYesToken contract address 0x...

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the paid x402/USDC-on-Base requirement, the underlying RPC mechanism, and the shape of the result. It does not cover error behavior (invalid address, non-ERC20 contract, symbol lookup failure) or rate limits, which keeps it short of a 5.

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 sentence with no wasted wording, and the return fields are listed compactly. The cost preamble precedes the purpose, which is defensible as a gating fact but slightly delays the tool's identity.

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?

For a two-parameter read tool with no output schema, the description covers chain scope, payment cost, mechanism, and return values (raw + human balance, decimals, symbol). Only failure modes and latency/rate behavior are absent.

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 description coverage is 100%, so both parameters are already documented; the description only adds that the address must be a Base address and that contract is the token contract — refinement, not new semantics. Baseline 3 applies.

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: fetch an on-chain ERC20 token balance for a Base address, implemented via eth_call balanceOf. It is easy to tell apart from siblings like get_crypto_price (market price), get_base_gas, or get_wallet_profile.

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 only implied by 'on-chain ERC20 token balance for any Base address'; there is no explicit when-to-use or when-not guidance, and no sibling is named as an alternative (e.g. get_crypto_price for prices rather than balances). The $0.02 cost does effectively signal that this is a metered call, not a fallback.

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.

Resources