Skip to main content
Glama

get_token_balance

Get ERC-20 token balance on Base. decimals_assumed=6 (USDC-style). Use balance_raw for exact integer.

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": "get_token_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesToken contract (USDC: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913)
addressYesWallet address

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It usefully discloses the chain (Base) and a decimal assumption ('decimals_assumed=6'), warning that non-6-decimal tokens need care, but it leaves the 'balance_raw' reference undefined and does not describe error or permission 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?

Two compact sentences, front-loaded with scope and chain. The final clause about 'balance_raw' is cryptic and slightly undermines an otherwise efficient structure.

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?

No output schema or annotations exist, so the description should explain the returned balance shape. The decimals assumption is valuable, but referring to an undefined 'balance_raw' without stating whether it is a response field or another tool leaves a key gap.

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 address and token are already documented with examples. The description adds a return-value caveat about decimals but does not add meaning to the two input parameters themselves, so baseline 3 applies.

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?

States a specific verb and resource ('Get ERC-20 token balance') plus the chain ('on Base'), which naturally separates it from get_eth_balance. It does not explicitly name a sibling or boundary, so not a 5.

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 implied by the resource name: query an ERC-20 balance rather than ETH. There is no explicit when-to-use, when-not-to-use, or alternative routing guidance.

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