Skip to main content
Glama
chia-mcp

chia-mcp

Official
by Chia-Network

get_block_records

Read-only

Retrieve block record metadata for a range of Chia block heights by supplying a start and end height, so you can inspect blocks in a specific span without running a local node.

Instructions

Get block records for a range of heights [start, end). Returns an array of block record metadata. Keep ranges small (≤20 blocks) to avoid large responses.

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": {
      "start": "<start>",
      "end": "<end>"
    },
    "name": "get_block_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesEnd height (exclusive)
startYesStart height (inclusive)

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?

Annotations already establish readOnlyHint=true, so the safety profile is covered. Beyond that, the description adds two pieces of behavioral context not in the structured data: the return shape ('array of block record metadata') and a response-size/performance ceiling on range width, which directly affects how an agent should call it.

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 purpose, then the return type, then the practical constraint. Nothing is redundant or misplaced.

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 two-parameter read-only tool with fully covered schema and no output schema, the definition covers purpose, scope, return type, and the main invocation pitfall. Minor gap: 'block record metadata' is not itemized, though that is largely the return-value domain the missing output schema would normally handle.

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 start and end already documented as inclusive/exclusive in the schema. The description's restatement of '[start, end)' adds clarity but no new meaning, so the baseline 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 and resource ('Get block records') plus the exact scope ('a range of heights [start, end)'), so an agent knows precisely what it returns. It does not, however, distinguish itself from closely named siblings such as get_block_record, get_block_record_by_height, or get_blocks, leaving the agent to infer the difference.

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?

It supplies one concrete operational guideline ('Keep ranges small (≤20 blocks) to avoid large responses'), which is genuinely useful for calling it well. But there is no statement of when to prefer this over the singular get_block_record or get_blocks, and no exclusion conditions, so usage is only implied.

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