Skip to main content
Glama

get_transaction_from_pending

Read-onlyIdempotent

Retrieve details of a specific TRON transaction from the pending pool by its transaction ID to inspect unconfirmed activity before it is mined.

Instructions

Get the details of a specific transaction from the pending pool by its transaction ID.

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": {
      "txId": "<txId>"
    },
    "name": "get_transaction_from_pending"
  }
}

Input Schema

NameRequiredDescriptionDefault
txIdYesThe transaction ID (hash) to look up in the pending pool
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.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety and side-effect profile is fully covered without the description. The description adds no behavioral context of its own — nothing about what happens when the txId is absent from the pool (empty result vs. error) or that pending-pool state is volatile. Small credit for the pool-specific scope.

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 qualifier 'pending pool' and the lookup key come early. It is efficient, though the brevity leaves behavioral gaps unaddressed rather than the sentence containing any waste.

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?

This is a simple, two-parameter read with a fully documented schema and rich annotations, so most agent needs are met structurally. What is missing is the not-found/error outcome and confirmation that the result is a snapshot of a volatile pool — modest but real gaps for a tool whose entire novelty is the pending scope.

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%: txId carries a regex/length constraint and a description, and network documents its mainnet default. The description only restates 'by its transaction ID' and never mentions the optional network parameter, so it adds no meaning beyond the schema. Baseline 3 applies.

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 names a specific verb ('Get'), resource ('transaction'), and scope ('from the pending pool ... by its transaction ID'), which lets an agent separate it from confirmed-chain siblings like get_transaction or get_transaction_by_id. It stops short of naming those siblings explicitly, so it is clear but not fully differentiated.

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?

Usage is implied by the 'pending pool' scoping — use it when the transaction has been broadcast but not yet mined. There is no explicit statement of when to prefer get_transaction instead, nor any prerequisite such as the transaction needing to be broadcast first, so guidance is only implicit.

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