Skip to main content
Glama

get_pending_transactions

Read-only

Fetches pending transaction IDs from the TRON mempool so you can monitor unconfirmed transactions awaiting block inclusion.

Instructions

Get the list of transaction IDs currently in the pending pool (mempool).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_pending_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
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=true, destructiveHint=false, and openWorldHint=true, and the description's 'currently in the pending pool' is consistent with the non-idempotent hint since mempool contents change between calls. Beyond that it says nothing about result volume, pagination, or whether the snapshot is taken at a single point in time — meaningful gaps for a live, potentially large list.

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 the scope constraint stated immediately and no redundant or filler wording.

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?

With no output schema, the description does useful work by specifying that the return value is transaction IDs rather than full transaction objects. However, for a mempool listing that can be large and volatile, it omits any statement about result size limits, ordering, or snapshot semantics, leaving the agent unable to anticipate the response.

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 coverage is 100% and the single optional 'network' parameter is fully documented in the schema, including its mainnet default, so the baseline of 3 applies. The description adds no network-scoping context of its own.

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?

Names a specific verb and resource ('Get the list of transaction IDs') and pins scope with 'currently in the pending pool (mempool)', which lets an agent distinguish it from get_pending_size and get_transaction_from_pending. The qualifier 'transaction IDs' clarifies it returns identifiers rather than full transactions, though siblings are never named explicitly.

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. The description never routes the agent between this tool and obvious alternatives such as get_pending_size or get_transaction_from_pending, so the agent must infer the distinction from names 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