Skip to main content
Glama

get_account_internal_transactions

Read-onlyIdempotent

Retrieve TronGrid-indexed internal transactions triggered by smart contract execution for a TRON account, with pagination, timestamp filtering, and confirmation status options.

Instructions

Get internal transactions (triggered by smart contract execution) for an account from TronGrid indexed data. Supports pagination via limit + fingerprint. Default 20, max 200.

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_internal_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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds that results come from 'TronGrid indexed data' (hinting at indexer coverage/lag) and documents pagination mechanics (limit + fingerprint, default 20, max 200), but says nothing about auth requirements, rate limits, or what a page contains beyond the transaction list.

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?

Two short sentences with the resource defined first and pagination behavior second. No filler, no repetition, and the most decision-relevant information is front-loaded.

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 9-parameter read-only query tool with full schema coverage and no output schema, the description covers the essential cross-parameter behavior (pagination) and the data provenance. It leaves defaults for orderBy and the onlyConfirmed/onlyUnconfirmed interplay to the schema, which is acceptable given 100% coverage.

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 most parameter meaning is already documented. The description's only real addition is pairing 'limit + fingerprint' as the pagination mechanism and restating the default/max limits, which is worthwhile but largely duplicates the schema's own limit description.

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 gives a specific verb and resource ('Get internal transactions') and clarifies the concept with '(triggered by smart contract execution)', plus a scope constraint ('for an account'). It does not explicitly name the sibling get_contract_internal_transactions to distinguish address-scoped from contract-scoped queries, so it falls short of a 5.

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?

The description implies usage by saying it is for 'an account' and by explaining pagination, but it never states when to prefer this over get_contract_internal_transactions or get_account_transactions, nor any prerequisites for paging. Guidance is implied rather than stated.

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