Skip to main content
Glama

get_block_by_id

Read-onlyIdempotent

Query a TRON block by its 64-character hash and retrieve its block header and transaction list for blockchain inspection.

Instructions

Query block by block ID (hash). 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": {
      "value": "<value>"
    },
    "name": "get_block_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesBlock hash / ID (64-char hex string)
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.5/5.0
Behavior3/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 covered. The description adds real value by disclosing the return shape ('block header and transaction list') in the absence of an output schema, but it says nothing about unknown-hash behavior, result size, or whether the transaction list is truncated or paginated.

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 tight sentences with no filler, and the identification of the lookup key is front-loaded before the return description. Appropriate size for a simple lookup tool.

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 straightforward, well-annotated two-parameter lookup with full schema coverage, the definition tells the agent what it retrieves and what comes back. The remaining gaps (error semantics, result size limits, multi-network behavior) are minor rather than blocking.

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 'value' documented as a 64-char hex block hash and 'network' defaulting to mainnet. The description's 'block ID (hash)' merely restates the schema and never mentions the optional network parameter, so no meaning is added beyond structured fields.

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 (query) and resource (block) and pins the lookup key to a block ID/hash, which implicitly separates it from the by-number and latest-block siblings. It stops short of naming an alternative explicitly, so differentiation is inferable rather than stated.

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 phrase 'by block ID (hash)' implies the case where you already have a hash rather than a height, which is useful context. However, there is no explicit when-to-use/when-not guidance, no mention of when to prefer get_block_by_num or get_latest_block, and no prerequisites or error conditions.

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