Skip to main content
Glama

get_pending_size

Read-only

Retrieve the number of transactions currently in the TRON pending pool (mempool) to assess network congestion and pending activity.

Instructions

Get the number of transactions 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_size"
  }
}

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.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, non-destructive and non-idempotent, so safety is covered. The word 'currently' is the one addition, hinting that the value is a volatile snapshot, which explains the non-idempotent hint, but nothing is said about freshness, polling recommendations, or failure behavior on an unavailable network.

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?

One front-loaded sentence with zero redundant wording; the parenthetical '(mempool)' adds a useful synonym rather than noise.

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 single-value read with one optional parameter, no output schema and full annotation coverage, the description states enough to call it correctly and even indicates the return value is a number. Only the relationship to sibling pending-pool tools is left implicit.

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 already carries its own description and default. The tool description adds no meaning beyond the schema, so the 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?

States a specific verb and resource: the count of transactions currently in the pending pool (mempool). This is distinguishable from get_pending_transactions in principle, but the description never names that sibling, so the reader must infer that this returns only a size while the other returns contents.

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 guidance: nothing says to call this for mempool congestion checks rather than get_pending_transactions or get_transaction_from_pending. The only signal is the implied context of 'currently in the pending pool', which is not guidance.

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