Skip to main content
Glama

get_block_by_latest_num

Read-only

Fetch a specified number of recently solidified TRON blocks in descending height order for blockchain data inspection or analysis.

Instructions

Retrieve the most recent N blocks, starting from the latest solidified block in descending order of 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_block_by_latest_num"
  }
}

Input Schema

NameRequiredDescriptionDefault
numYesNumber of latest blocks to retrieve (1-100)
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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered; the description adds genuinely new behavioral context by disclosing the starting anchor (latest solidified block) and result ordering (descending height). It stops short of explaining what happens near chain head, pagination behavior, or what a returned block contains.

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 sentence with the resource, the anchor, and the ordering all front-loaded; no filler, no redundancy, and no ambiguity requiring a second read.

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 two-parameter read tool with full annotation coverage this covers the essential call semantics, but with no output schema the description leaves the agent guessing about the shape of a returned block and about ordering/volume limits beyond the schema's maximum of 100. Adequate but with a clear gap on return-value expectations.

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' (1-100 bounds) and 'network' (defaults to mainnet) fully documented in the schema. The description restates 'N blocks' but adds no syntax, format, or constraint detail beyond what the schema already supplies, so 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 gives a specific verb (retrieve) and resource (the most recent N blocks) with an explicit anchor point (latest solidified block) and ordering (descending height). It is clearly distinguishable from single-block siblings like get_latest_block or get_block_by_num by its plural, N-parameterized scope, though it never names those siblings 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 implied rather than stated: an agent can infer this is for fetching a batch of recent blocks, but there is no explicit 'use this when / use X instead when' guidance, and no note about when to prefer get_latest_block or get_block_by_limit_next. No prerequisites or exclusions are given.

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