Skip to main content
Glama
chia-mcp

chia-mcp

Official
by Chia-Network

get_block_record

Read-only

Retrieve block metadata by header hash, including height, weight, timestamp, fees, and farmer/pool puzzle hashes, without fetching a full block.

Instructions

Get a block record by its header hash. Returns block metadata (height, weight, timestamp, fees, farmer/pool puzzle hashes). Lighter than a full block.

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": {
      "header_hash": "<header_hash>"
    },
    "name": "get_block_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
header_hashYesThe header hash of the block (0x-prefixed, 32 bytes hex)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint already declares this a safe read, so the description only needs to add context. It usefully names the returned fields and positions the result as lighter than a full block, but says nothing about behavior when the hash is unknown or about payload size/limits.

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, front-loaded with the identifying operation, then return contents, then a comparative note. No filler or redundancy.

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 with no output schema, the description covers what is returned and how it compares to a fuller block, which is what an agent needs to select and call it. Missing only the not-found behavior.

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 header_hash parameter is fully documented in the schema, including the 0x-prefixed 32-byte hex pattern. The description only restates that lookup is by header hash, adding no format guidance beyond the schema.

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 and resource ('Get a block record by its header hash') and enumerates what the record contains. The lookup key implicitly distinguishes it from get_block_record_by_height, but the distinction is left for the agent to infer 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 a full block' hints at a tradeoff against get_block, but there is no explicit when-to-use or when-not-to-use guidance. The agent must decide on its own between this, get_block, get_block_records, and get_block_record_by_height.

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