Skip to main content
Glama

get_account_trc20_balances

Read-onlyIdempotent

Retrieve all TRC20 token balances for a TRON account from indexed data, returning contract addresses and raw balances; use get_token_balance for token metadata and details.

Instructions

Get all TRC20 token balances for an account from TronGrid indexed data. Returns only token contract addresses and raw balances — does NOT include token metadata (name, symbol, decimals). Use get_token_balance for detailed info on a specific token.

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

Input Schema

NameRequiredDescriptionDefault
addressYesAccount address (base58 T-address or hex 41-prefixed)
networkNoNetwork name. Defaults to mainnet.
onlyConfirmedNoOnly return confirmed data

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

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: the result contains only contract addresses and raw balances with no name/symbol/decimals, warning the agent it must resolve metadata elsewhere and interpret undecorated integers. It says nothing about pagination, result caps, or indexing lag.

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?

Three short sentences, front-loaded with the core action, then the important limitation, then the alternative. Every sentence carries distinct information with no repetition of the name or schema.

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?

With no output schema, the description takes on the burden of describing the return shape and does so by naming the fields returned and the fields deliberately omitted. Only secondary details — pagination behavior, whether zero-balance tokens appear, and indexing freshness — are left unaddressed for a 3-parameter read tool.

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% — address formats, network default, and onlyConfirmed are all documented in the schema. The description adds no further meaning about these parameters, so the baseline of 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 ('Get all TRC20 token balances for an account') plus the data source ('TronGrid indexed data'), which distinguishes it from get_account_balance (native TRX) and get_token_balance (single token). An agent can identify the tool's scope without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent to get_token_balance when detailed info on a specific token is needed, giving a concrete alternative and the condition that selects it. It does not spell out when-not-to-use cases such as preferring transaction history tools, so it falls just short of full coverage.

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