Skip to main content
Glama

get_account_trc20_transactions

Read-onlyIdempotent

Retrieve an account's TRC20 token transfer history with token details, human-readable values, pagination, timestamp filters, and confirmed-status options.

Instructions

Get TRC20 token transfer history for an account from TronGrid indexed data. Returns token transfer details including token info (name, symbol, decimals) and human-readable values. Supports pagination via limit + fingerprint. Default 20 results, max 200 per page.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax transactions per page (default 20, max 200)
addressYesAccount address (base58 T-address or hex 41-prefixed)
networkNoNetwork name. Defaults to mainnet.
orderByNoSort field, e.g. 'block_timestamp,desc'
fingerprintNoPagination token from previous response
maxTimestampNoFilter: maximum block timestamp (ms)
minTimestampNoFilter: minimum block timestamp (ms)
onlyConfirmedNoOnly return confirmed transactions
contractAddressNoFilter by specific TRC20 token contract address
onlyUnconfirmedNoOnly return unconfirmed transactions

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.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds value beyond them: it discloses the indexed TronGrid data source, pagination mechanics (limit + fingerprint), and the default/max page size. It stops short of noting indexing lag or rate limits, which would matter for a paginated indexed-data endpoint.

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?

Four short sentences, front-loaded with the core purpose, then return shape, then pagination. The final sentence duplicates the schema's limit description, a small redundancy, but overall it is tight and scannable.

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 ten parameters, no output schema and no enums, the description carries the return-value burden well by naming token info (name, symbol, decimals) and human-readable values. Gaps remain around default ordering and valid network values, but an agent has enough to call it correctly.

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 all ten parameters are already documented, including limit, address, network, orderBy, fingerprint and timestamp filters. The description's mention of limit/fingerprint pagination and the 20/200 bounds merely restates schema content, adding no new semantics.

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 TRC20 token transfer history for an account'. The TRC20-transfer scope is distinguishable from sibling balance/transaction tools without opening the schema, though the description never names a sibling to contrast with.

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 scope ('TRC20 token transfer history ... from TronGrid indexed data') but there is no explicit when-to-use vs when-not guidance, nor any pointer to get_account_transactions or get_account_trc20_balances for the non-TRC20 or balance cases.

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