Skip to main content
Glama

get_transaction_info

Read-onlyIdempotent

Retrieve TRON transaction details by hash, including confirmation status, energy usage, and logs. Use it to verify whether a transaction succeeded and inspect its on-chain effects.

Instructions

Get transaction info (receipt/confirmation status, energy usage, logs).

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": {
      "txHash": "<txHash>"
    },
    "name": "get_transaction_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
txHashYesTransaction hash
networkNoNetwork name. Defaults to mainnet.

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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful return-content context (receipt/confirmation status, energy usage, logs) which matters because there is no output schema. It says nothing about behavior for unknown or pending hashes.

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?

A single front-loaded sentence with no filler; the parenthetical efficiently lists the return payload. It is on the terse side, leaving little room for routing detail, but nothing is wasted.

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

Completeness3/5

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

For a two-parameter read tool with full schema coverage, the description covers purpose and payload, but omits the sibling disambiguation an agent needs in a catalog with many similarly named transaction tools. Missing error/empty-result behavior is a modest gap given annotation 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%, with both txHash and network documented in the schema including the mainnet default, so the baseline of 3 applies. The description adds no semantics beyond the schema, such as accepted hash format or cross-network lookup behavior.

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 info') and enumerates the payload it returns (receipt/confirmation status, energy usage, logs). It does not distinguish itself from near-identical siblings such as get_transaction_info_by_id or get_transaction_info_by_block_num, so an agent cannot tell from the description that this one is hash-keyed.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no named alternative. The required txHash parameter implies the hash-keyed lookup path, but the agent gets no help choosing between this, get_transaction_info_by_id, get_transaction_from_pending, or the broader get_transaction tools.

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