Skip to main content
Glama

get_account_transactions

Read-onlyIdempotent

Retrieve an account's TRON transaction history from TronGrid indexed data, including TRX transfers and contract calls, with pagination and timestamp or confirmation filters.

Instructions

Get transaction history for an account from TronGrid indexed data. Returns all transaction types (TRX transfers, contract calls, etc.). 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_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
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.8/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 operational context beyond that: the indexed-data source, page size defaults and hard cap (20 default, 200 max), and the pagination mechanism. It stops short of noting rate limits or how incomplete/unconfirmed data is handled.

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, zero filler, and the core purpose is front-loaded before pagination details. Every sentence contributes either scope or an operational constraint.

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 nine-parameter read tool with no output schema, the definition covers what is returned at a coarse level (all transaction types) and how paging works, which is enough to invoke it correctly. The remaining gap is that the response shape is only gestured at, so an agent cannot anticipate the fields of a returned transaction without calling it.

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 nine parameters are already documented in-schema, including limit bounds and fingerprint meaning. The description restates the limit default/max and the fingerprint pagination contract but adds no meaning beyond the schema (e.g., orderBy syntax, timestamp filter interaction, or behavior when both onlyConfirmed and onlyUnconfirmed are set). 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 transaction history for an account") plus the data source (TronGrid indexed data) and scope (all transaction types, with examples). The "all transaction types" phrasing implicitly distinguishes it from the filtered siblings like get_account_trc20_transactions and get_account_internal_transactions, but no sibling is named 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 context is implied by the scope statement — an agent can infer this is the right tool for a general, unfiltered history pull while the typed siblings cover TRC20/internal subsets. However there is no explicit when-to-use/when-not guidance or named alternative, so routing to the correct sibling is left to inference.

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