Skip to main content
Glama

get_contract_internal_transactions

Read-onlyIdempotent

Retrieve internal transactions triggered by smart contract execution for a TRON contract address from TronGrid indexed data, with pagination and timestamp filters.

Instructions

Get internal transactions (triggered by smart contract execution) for a contract address 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_contract_internal_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax transactions per page (default 20, max 200)
addressYesContract 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, destructiveHint=false and openWorldHint, so the safety profile is covered structurally. The description adds only the pagination mechanic (limit + fingerprint, default 20, max 200) and the 'TronGrid indexed data' provenance, both of which are already conveyed by the schema; it says nothing about whether unconfirmed data appears by default or what the response looks like.

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 sentences, front-loaded with the resource and scope, then the pagination contract. Every clause carries information and there is no filler.

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 nine parameters fully described in the schema and rich annotations, the description covers what an agent needs to select and call it: scope, data source, and pagination loop. Since no output schema exists, a brief note on the returned fields or how to detect the last page would have closed the remaining gap.

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 including address format, network default, orderBy, timestamp filters and confirmation flags are already documented inline. The description only restates the limit defaults, adding no meaning beyond the schema, so the baseline of 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?

The description states a specific verb and resource ('Get internal transactions ... for a contract address') and clarifies the parenthetical semantics ('triggered by smart contract execution'), which meaningfully separates it from get_contract_transactions (top-level calls) and get_account_internal_transactions (account-scoped). It does not name those siblings explicitly, so the differentiation is inferred rather than stated.

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 phrase 'for a contract address from TronGrid indexed data', which tells an agent this is the contract-side lookup against indexed (not live/pending) data. However, there is no explicit when-to-use vs. the account variant or the broader transaction tools, and no stated prerequisites or failure conditions.

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