Skip to main content
Glama

get_transaction_info_by_block_num

Read-onlyIdempotent

Retrieve transaction receipts and details for every transaction in a specified TRON block height, with an optional network parameter for mainnet or other networks.

Instructions

Get TransactionInfo (receipts) for all transactions in a specific block height.

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": {
      "num": "<num>"
    },
    "name": "get_transaction_info_by_block_num"
  }
}

Input Schema

NameRequiredDescriptionDefault
numYesBlock height number
networkNoNetwork name. Defaults to mainnet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.9
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / num / maximum
      Added value: +9007199254740991
  2. First observedv1.1.7

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds that results are TransactionInfo receipts for every transaction in the block, which is useful output context, but says nothing about volume, ordering, or pagination for blocks with many transactions.

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 scope qualifier follows immediately after the core verb. Slightly terse for a tool whose result set can be large, but nothing is wasted.

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 two-parameter read query with full schema coverage, no output schema, and annotations covering behavior, the description supplies the one thing the structured fields don't: that the result is receipts for all transactions in the block. Only the lack of payload-size/pagination context is a minor gap.

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%, with both 'num' (block height) and 'network' (defaults to mainnet) documented in the schema itself. The description adds no extra semantics beyond what the schema provides, 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?

The description names a specific verb and resource ('Get TransactionInfo (receipts)') and scopes it to 'all transactions in a specific block height', which implicitly separates it from the by-id sibling. It stops short of explicitly naming an alternative, 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?

The block-height keying implies when this tool applies (you have a block number, not a transaction hash), but there is no explicit when-to-use/when-not-to-use statement or named alternative such as get_transaction_info_by_id.

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