Skip to main content
Glama

Find Tron transactions

portal_tron_query_transactions
Read-only

Query raw Tron transactions: native TRX transfers, TRC-10 asset transfers, TriggerSmartContract calls by contract and method, or any contract type, with optional inline logs and internal transactions.

COMMON USER ASKS:

  • Recent native TRX transfers

  • USDT transfer calls in a block window

  • TRX sent from one wallet

FIRST CHOICE FOR:

  • native TRX transfers, TRC-10 transfers, and smart-contract calls on Tron

  • who sent TRX to an address on Tron, or which wallets called a Tron contract

WHEN TO USE:

  • You need raw Tron transaction records with sender, recipient, amount in TRX, fee, energy, and success.

  • You want native TRX transfers to or from a wallet in a bounded window.

  • You want calls to a Tron contract such as USDT filtered by method (transfer, approve) or caller.

  • You want TRC-10 asset transfers by asset id.

DON'T USE:

  • You need TRC-20 token events; those are logs, so use portal_tron_query_logs.

  • You need an Ethereum-compatible network; use portal_evm_query_transactions.

EXAMPLES:

  • Recent native TRX transfers: {"network":"tron-mainnet","timeframe":"5m","kind":"transfer","limit":20}

  • USDT transfer calls in a block window: {"network":"tron-mainnet","from_block":84000000,"to_block":84000010,"contract_addresses":["TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t"],"method":"transfer","limit":20}

  • TRX sent from one wallet: {"network":"tron-mainnet","timeframe":"1h","kind":"transfer","from_addresses":["TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t"],"limit":20}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoWhich Tron transaction family to query: transfer (native TRX), transfer_asset (TRC-10), trigger_smart_contract (contract calls), all (any contract type, filter by types only). auto picks from the filters you pass.auto
assetNoFILTER (transfer_asset): TRC-10 asset id such as 1005157, or the raw hex asset name.
limitNoMax transactions to return (default: 20, max: 25)
typesNoFILTER (kind=all): Tron contract types such as TransferContract, TriggerSmartContract, DelegateResourceContract.
cursorNoContinuation cursor from a previous response
methodNoFILTER (trigger_smart_contract): method alias such as transfer, approve, transferFrom, or a 4-byte sighash.
networkNoNetwork name (default: tron-mainnet). Optional when continuing with cursor.
sighashNoFILTER (trigger_smart_contract): 4-byte method selectors, with or without 0x. Merges with method.
to_blockNoEnding block number. Tron produces a block every 3 seconds.
timeframeNoTime range (e.g., '5m', '1h'). Alternative to from_block/to_block.
from_blockNoStarting block number
include_logsNoAttach the event logs each transaction emitted
to_addressesNoFILTER (transfer, transfer_asset): recipient addresses in any accepted form.
to_timestampNoEnding timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now".
finalized_onlyNoOnly query finalized blocks
from_addressesNoFILTER: sender or caller addresses. Accepts Base58 (T...), 41-prefixed hex, or 0x/bare 20-byte hex.
from_timestampNoStarting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago".
max_scan_blocksNoSafety cap for filtered latest-first scans. Default: min(window, 50000).
response_formatNoResponse format: defaults to 'compact' for chat-friendly output. Use 'summary' for counts by type, TRX moved, and top callers.
contract_addressesNoFILTER (trigger_smart_contract): called contract addresses in any accepted form, e.g. USDT.
include_internal_transactionsNoAttach the internal transactions of each transaction

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
_uiNoChart, table, and follow-up presentation metadata.
_appNoSQD Explorer identity and host-render state.
_llmNoHints to locate the primary evidence.
_metaNoNetwork, block range, timing, and row counts.
errorNoStructured failure details.
itemsNoPrimary rows for list results.
valueNoPrimary scalar result.
answerNoAnswer grounded in the returned data.
_noticeNoLimitation or truncation notice.
_serverNoSQD server name, exact version, and git commit.
displayNoLabels for presenting the result.
_noticesNoLimitation or truncation notices.
_summaryNoHuman-readable summary.
_coverageNoWindow and result completeness.
_evidenceNoReplayable arguments, digest, row count, and receipt.
_orderingNoOrdering guarantees.
_executionNoBounded execution and scan details.
_freshnessNoFreshness and finality.
next_stepsNoSafe follow-up actions and continuation guidance.
_paginationNoPagination state and next_cursor.
investigationNoEvidence paths, pivots, and limitations.
pipes_handoffNoSQD Pipes guidance for custom data needs.
_tool_contractNoTool identity, intent, and chain families.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds meaningful context beyond that: it queries raw transactions, optionally includes logs and internal transactions, and can return summary/compact formats. It also clarifies the scope of what counts as a Tron transaction and what does not, which is valuable behavioral information.

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?

The description is well-structured with clear sections (COMMON USER ASKS, FIRST CHOICE FOR, WHEN TO USE, DON'T USE, EXAMPLES) and front-loads the core purpose. There is some redundancy between 'FIRST CHOICE FOR' and 'WHEN TO USE', but overall each section earns its place and the examples are compact and illustrative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (21 parameters, 0 required, many filters), the description is exceptionally complete. It covers common intents, exact example payloads, exclusions, and alternatives. The input schema covers all parameter semantics, and an output schema exists, so nothing critical is missing for an agent to invoke this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents every parameter. The description adds value by showing realistic parameter combinations in examples, mapping common user asks to concrete JSON payloads, and clarifying which filters work with which kind values. It doesn't deeply explain every parameter, but it doesn't need to given the high schema coverage.

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?

The description opens with a specific verb and resource: 'Query raw Tron transactions', then enumerates exact families (native TRX transfers, TRC-10 transfers, TriggerSmartContract calls, any contract type). It also distinguishes itself from siblings by explicitly noting TRC-20 logs belong to portal_tron_query_logs and Ethereum-compatible networks belong to portal_evm_query_transactions.

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

Usage Guidelines5/5

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

The description gives explicit 'WHEN TO USE' bullets, a 'DON'T USE' section naming concrete alternatives, and a 'FIRST CHOICE FOR' section. This leaves little ambiguity about when an agent should select this tool over sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.