Skip to main content
Glama

get_transaction_info_by_id

Read-onlyIdempotent

Retrieve a TRON transaction receipt by hash to inspect energy usage, fees, logs, and confirmation status. Verify transaction outcomes and costs.

Instructions

Query transaction receipt including energy usage, fee, logs, and confirmation status by transaction hash.

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": {
      "value": "<value>"
    },
    "name": "get_transaction_info_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesTransaction hash (txID)
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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context about returned receipt fields, but it does not describe behavior for missing, pending, or failed transactions. With annotations carrying the main behavioral burden, a 3 is appropriate.

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?

The description is a single front-loaded sentence with no wasted wording. It puts the operation and lookup key first, followed by the returned data categories.

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 simple read-only lookup with only two fully documented parameters and clear safety annotations, the description covers the essential purpose and lists the main returned receipt fields despite there being no output schema. It is nearly complete, though it could better explain how this tool relates to similar transaction lookup siblings.

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%, and both parameters are documented there, including the transaction hash and optional network default. The description reinforces that lookup is by transaction hash but adds no details about network selection or hash formatting beyond the schema. This meets the baseline of 3 when the schema already provides full parameter semantics.

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 uses a specific verb and resource: query a transaction receipt by transaction hash. It also names the key receipt contents (energy usage, fee, logs, confirmation status), making the tool's purpose clear. However, it does not explicitly distinguish itself from siblings such as get_transaction_by_id or get_transaction_info.

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 phrase 'by transaction hash' implies the usage condition: call this when you have a transaction hash and need receipt data. The description does not explicitly state when to use this instead of related transaction or event lookup siblings, so guidance remains implied rather than explicit.

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