Skip to main content
Glama
chia-mcp

chia-mcp

Official
by Chia-Network

get_block_record_by_height

Read-only

Retrieve block metadata by height, including header hash, weight, timestamp, fees, and farmer/pool puzzle hashes. Use it for lighter queries than fetching full blocks.

Instructions

Get a block record at a specific height. Block records contain metadata like header hash, height, weight, timestamp, fees, and farmer/pool puzzle hashes. Lighter than full blocks.

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": {
      "height": "<height>"
    },
    "name": "get_block_record_by_height"
  }
}

Input Schema

NameRequiredDescriptionDefault
heightYesBlock height (0-indexed from genesis)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.8/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes the safety profile, and the description adds genuine context beyond it: what a block record contains (header hash, height, weight, timestamp, fees, farmer/pool puzzle hashes) and that it is a lighter payload than a full block. It stops short of noting behavior for out-of-range heights or genesis-edge cases.

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?

Three short sentences, purpose front-loaded, with the payload contents and the weight comparison following in order of decreasing importance. No filler or restatement of the tool name beyond the first clause.

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 single-parameter read tool with no output schema, the description compensates well by enumerating the returned metadata fields and characterizing payload size. The remaining gap is error/edge behavior for heights outside the chain, which a calling agent would have to discover.

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% and the single parameter is documented with a 0-indexed genesis note, so the schema carries the burden. The description's 'at a specific height' adds no format or range detail beyond what the schema already states, so the baseline of 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 a block record at a specific height') and distinguishes the result from a full block by noting block records are metadata-only and 'Lighter than full blocks.' It does not explicitly contrast with the closest sibling get_block_record (which presumably keys off a header hash), so the differentiation is implied 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?

'Lighter than full blocks' implies a preference for this tool when full block data is not needed, which is useful but indirect. There is no explicit when-to-use/when-not guidance and no named alternative such as get_block for full bodies or get_block_record for header-hash lookups, leaving the agent to infer.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.