Skip to main content
Glama

get_block_by_num

Read-onlyIdempotent

Query a TRON block by height to retrieve its header and transaction list. Use it to inspect block data for a specified height and network.

Instructions

Query block by block height. Returns block header and transaction list.

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_block_by_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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description's only addition is the return shape (block header and transaction list), which is useful given no output schema, but it says nothing about behavior on an out-of-range or nonexistent height, or about pagination/size of the transaction list.

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?

Two short sentences with no filler, and the what-it-does statement is front-loaded ahead of the return description. It is lean to the point of being terse, but no sentence is wasted.

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?

For a simple read-only lookup with full schema coverage and no output schema, the definition covers purpose and return contents adequately. It is still thin on edge behavior (height not found, network selection nuances beyond the schema default) that an agent would want before calling.

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%, so both parameters are already documented in the schema; baseline is 3. The phrase "by block height" restates the num parameter's purpose without adding format, range, or cross-network semantics beyond what the schema provides.

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?

"Query block by block height" names a specific verb and resource, and "by block height" implicitly separates it from siblings keyed by id or latest number. The second sentence states what comes back (header plus transaction list), so an agent can identify the tool without opening the schema, though no sibling is 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: needing a block addressed by height is the condition for calling it, and the height-based keying hints that get_block_by_latest_num or get_block_by_id are the alternatives. There is no explicit when-to-use/when-not statement or prerequisite 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