Skip to main content
Glama

get_token_balance

Read-onlyIdempotent

Retrieve the TRC20 token balance for a wallet address by specifying the token contract address and optional network. Use it to check token holdings on TRON.

Instructions

Get the TRC20 token balance for an address

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

Input Schema

NameRequiredDescriptionDefault
addressYesThe wallet address
networkNoNetwork name. Defaults to mainnet.
tokenAddressYesThe TRC20 token contract address

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.9
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.1.7

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond that, saying nothing about return format, decimals, or behavior for unlisted/unknown token contracts.

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 front-loaded sentence with zero filler; the resource and scope come first. It is slightly thin rather than padded, so it stops short of a 5.

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 simple three-parameter read tool with full schema coverage and annotations, the description is adequate to invoke correctly. It is incomplete in that it never characterizes the returned value (e.g. balance vs. raw units), and there is no output schema to compensate.

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%, with all three parameters documented including the network default to mainnet. The description adds no meaning beyond the schema, so the 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?

The description states a specific verb and resource: 'Get the TRC20 token balance for an address'. Naming TRC20 and the token contract address distinguishes it from native-TRX balance tools like get_account_balance or get_balance, though it never names those siblings explicitly.

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 rather than stated: the required tokenAddress parameter signals 'one specific token, one address'. There is no explicit when-to-use/when-not guidance pointing to get_account_trc20_balances for multi-token listings, leaving the agent to infer the choice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools