Skip to main content
Glama

get_trc20_token_holders

Read-onlyIdempotent

Retrieves a TRC20 token contract's holder list with addresses and balances; supports pagination to page through large holder sets.

Instructions

Get token holder list for a TRC20 contract from TronGrid indexed data. Returns holder addresses and their balances. Supports pagination via limit + fingerprint.

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_trc20_token_holders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax holders per page (default 20, max 200)
addressYesTRC20 token contract address (base58 T-address or hex 41-prefixed)
networkNoNetwork name. Defaults to mainnet.
orderByNoSort field, e.g. 'balance,desc'
fingerprintNoPagination token from previous response

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

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that results come from TronGrid indexed data (implying an indexer-derived, potentially lagging view) and that paging is fingerprint-based, but says nothing about rate limits, result caps (the 200 maximum is only in the schema), or ordering defaults.

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, identity and source first, return payload second, pagination mechanism last. No filler or restated boilerplate; every sentence carries information.

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 read-only, single-resource query tool with a fully documented schema and no output schema, the description covers what it returns and how to iterate. The remaining gaps (ordering default behavior, whether unindexed or zero-balance holders appear) are minor for this complexity level.

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 each of the five parameters (address, limit, network, orderBy, fingerprint) is already documented in the schema. The description only reinforces that limit and fingerprint drive pagination, adding no semantics beyond what the schema states, which is the baseline 3.

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 uses a specific verb and resource: 'Get token holder list for a TRC20 contract,' and states the data source (TronGrid indexed data) plus the return payload (holder addresses and balances). This distinguishes it from balance-lookup siblings like get_token_balance and get_account_trc20_balances, though it never names those alternatives 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 by the resource scope (TRC20 holders) and the description explains the pagination loop via limit + fingerprint, but it gives no explicit when-to-use vs when-not guidance and does not point to any sibling alternative for related questions such as a single account's token balance.

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