Skip to main content
Glama

get_transaction_by_id

Read-onlyIdempotent

Retrieve TRON transaction status and details by transaction hash, with optional network selection, to verify or inspect on-chain activity.

Instructions

Query transaction status and content 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_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

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior, so the safety profile is fully covered without the description. The description adds the useful framing that both status and content are returned, but says nothing about behavior for unknown hashes, pending transactions, or failed lookups.

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?

A single front-loaded sentence with no filler; the verb, resource, and lookup key all appear before any qualifying clause. Nothing could be removed without losing information.

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 simple two-parameter read with full annotation coverage and no output schema, the description is adequate but thin. It lacks the disambiguation from sibling lookup tools that an agent in this catalog genuinely needs to select correctly.

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 only two parameters, both documented in the schema, so the baseline is 3. The description reinforces that 'value' is a transaction hash but adds no meaning for the optional 'network' parameter beyond the schema's default-to-mainnet note.

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 ('Query') and resource ('transaction status and content') and names the lookup key (transaction hash), so the agent knows exactly what this returns. It stops short of distinguishing itself from several close siblings such as get_transaction_info_by_id, get_transaction, and get_transaction_info, leaving ambiguity about which one to pick.

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 explicit when-to-use or when-not-to-use guidance, and no alternative is named despite the catalog containing multiple near-duplicate transaction lookup tools. The only implied guidance is that a transaction hash is the input, which an agent could infer from the schema alone.

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