Skip to main content
Glama

get_contract_transactions

Read-onlyIdempotent

Retrieve paginated transaction history for a TRON smart contract address, with timestamp and confirmation filters to inspect contract activity.

Instructions

Get transaction history for a smart contract from TronGrid indexed data. Unlike get_account_transactions, this aggregates transactions BY contract. 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_contract_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

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so safety is covered. The description adds genuinely useful behavioral detail: the data is TronGrid-indexed, paging is fingerprint-based, and page size is bounded at 20 by default with a hard cap of 200 — information absent from the annotations.

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 sentences, each earning its place: what it does, how it differs from the sibling, and how paging works. The differentiating clause is front-loaded before the operational detail, with no filler or restatement of the name.

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, fully schema-documented query tool with no output schema, the definition covers purpose, differentiation, and pagination adequately. The remaining gap is that it never characterizes the returned records (fields, ordering default, whether internal or TRC20 transfers are included), which would help an agent interpret results.

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 every one of the nine parameters is already documented, which sets the baseline at 3. The description reinforces the limit/fingerprint pagination contract (default 20, max 200) but adds no syntax or format detail beyond what the schema already states, and says nothing about the timestamp filters, ordering, or network selection.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 a smart contract") plus the data source (TronGrid indexed data). The second sentence explicitly contrasts the aggregation axis with get_account_transactions (BY contract vs. by account), so an agent can distinguish it from the closest sibling without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the alternative get_account_transactions and the condition that selects this tool instead (contract-scoped aggregation). It does not address other plausible lookalikes such as internal-transaction or TRC20 variants, but within the stated scope the routing guidance is clear and actionable.

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