Skip to main content
Glama

get_transaction

Read-onlyIdempotent

Retrieve transaction details from the TRON blockchain by transaction hash, with an optional network parameter defaulting to mainnet.

Instructions

Get transaction details 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": {
      "txHash": "<txHash>"
    },
    "name": "get_transaction"
  }
}

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

C2.9/5.0
Behavior2/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 fully covered elsewhere. The description adds no behavioral context of its own — no not-found behavior, no pending-vs-confirmed semantics, no cross-network caveat — so it contributes essentially nothing beyond the structured fields.

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 or redundancy. It is efficient, though the brevity edges into under-specification rather than disciplined conciseness given the crowded sibling namespace.

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

Completeness2/5

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

With roughly a dozen overlapping transaction-retrieval siblings and no output schema, the description needs to disambiguate scope (by hash vs id vs pending, which network, what is returned). It supplies none of that, leaving the agent to guess among alternatives.

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 (including the mainnet default) in the schema itself. The description only echoes the txHash lookup and says nothing about the network parameter, so baseline 3 applies — the schema does all the work.

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 details") plus the lookup key (transaction hash), so the operation itself is unambiguous. However, it does nothing to separate itself from near-identical siblings such as get_transaction_by_id, get_transaction_info, or get_transaction_from_pending, which an agent cannot distinguish from this sentence alone.

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 guidance, no exclusion of alternatives, and no mention of when a hash-based lookup is preferable to id- or block-based siblings. Nothing tells the agent whether this returns confirmed, pending, or either kind of transaction, which is exactly the decision the sibling set forces.

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