Skip to main content
Glama

get_block_by_limit_next

Read-onlyIdempotent

Retrieve TRON block objects from an inclusive start height up to an exclusive end height. Use it to list blocks within a specified height range for blockchain analysis.

Instructions

Retrieve a list of block objects within the specified block height range [startNum, endNum).

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": {
      "startNum": "<startNum>",
      "endNum": "<endNum>"
    },
    "name": "get_block_by_limit_next"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNumYesEnd block height (exclusive)
networkNoNetwork name. Defaults to mainnet.
startNumYesStart block height (inclusive)

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully covered. The description adds nothing beyond that: it does not disclose any cap on range size, ordering of results, pagination behavior, or what happens when the range extends beyond the chain tip.

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 sentence with no filler, and the resource is front-loaded before the range constraint. Nothing is redundant, though there is little structure to speak of beyond the one clause.

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?

There is no output schema, so the description's phrase 'list of block objects' is the only signal about return shape, which is minimally helpful but leaves ordering and size unspecified. For a tool that takes a height interval — a shape that invites arbitrarily large requests — the absence of any bound or pagination note is a real 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 description coverage is 100%, with both startNum (inclusive) and endNum (exclusive) documented directly in the schema. The description restates the half-open interval notation, which reinforces the boundary semantics but adds no meaning beyond what the schema already provides; the undocumented-in-description 'network' parameter is also covered by the schema. Baseline 3 is appropriate.

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 ('Retrieve') and resource ('block objects') with a clear scoping qualifier (block height range). It does not, however, distinguish this from siblings such as get_block_by_num, get_latest_block, or get_block_by_id, so an agent must infer the batch-range distinction on its own.

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?

No when-to-use guidance, no exclusions, and no mention of the sibling tools that retrieve blocks by number, id, or latest. The range notation implies a batch fetch, but the agent is given no stated rule for choosing this tool over a single-block fetch.

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