Skip to main content
Glama

edge-signals

erc20_balance

ERC20 balanceOf for a wallet and token contract on Base or Ethereum.

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

Input Schema

NameRequiredDescriptionDefault
chainNobase (default) or ethereum
tokenYesERC20 contract 0x
addressYesWallet 0x

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral burden, and 'balanceOf' does signal a read-only lookup with the chain scope spelled out. However, it omits practical behavior an agent needs: whether the result is raw base units or decimal-adjusted, what happens when the address or token is not a valid contract, and error conditions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the operation, operands, and chain scope are all stated immediately.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter read tool with full schema coverage this is close to adequate, but the absence of any note on return units (raw integer vs. decimals) or on how it differs from wallet_balances leaves real gaps for an agent choosing between balance tools.

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 a baseline of 3 applies, and the description adds a bit by mapping 'wallet and token contract' to the address/token parameters and confirming the chain scope that the schema already lists. It still adds no format or validation detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific operation ('ERC20 balanceOf'), the two resources it needs (wallet and token contract), and the supported chains. It is clear what the tool returns, but it never distinguishes itself from the sibling wallet_balances, which an agent could reasonably pick instead.

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: the agent must infer that this is the tool for a single-token balance versus a multi-token portfolio tool. There is no explicit when-to-use, when-not-to-use, or named alternative.

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