Skip to main content
Glama
chia-mcp

chia-mcp

Official
by Chia-Network

get_blocks

Read-only

Retrieve full Chia block data, including transactions, for a specified height range; request only up to three blocks at a time because complete blocks are large.

Instructions

Get full blocks for a range of heights [start, end). Returns complete block data including transactions. Keep ranges small (≤3 full blocks) as full blocks are large.

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_blocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesEnd height (exclusive)
startYesStart height (inclusive)
exclude_reorgedNoIf true, exclude blocks that were reorged (default: false)
exclude_header_hashNoIf true, exclude header hashes from the response (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

B3.4/5.0
Behavior3/5

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

Consistent with readOnlyHint=true. The description adds real value beyond annotations by warning that full blocks are large and including transactions, which shapes call sizing. It does not cover pagination, response shape, or what happens if the range spans hundreds of heights.

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?

Three short sentences, front-loaded with what is returned, then the size caveat. No filler; the only mild redundancy is 'full blocks' and 'complete block data including transactions' restating each other.

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?

There is no output schema, so the description must characterize the return value; it does so at a high level ('complete block data including transactions') but not structurally. The size warning partially compensates for the missing exclude_* parameter guidance, leaving it adequate rather than complete.

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%, so all four parameters (start, end, exclude_reorged, exclude_header_hash) are already documented in the schema. The description echoes the inclusive/exclusive range semantics but adds nothing about the two exclude_* flags, which affect response size meaningfully. 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?

States a specific verb and resource with explicit scope: 'Get full blocks for a range of heights [start, end)'. The range notation implicitly separates it from the single-block sibling get_block and from header-oriented tools like get_unfinished_block_headers, though no sibling is named.

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?

Gives a practical constraint ('Keep ranges small (≤3 full blocks)') which is genuinely useful operational guidance, but never states when to prefer get_block over this tool or when a range query is the wrong choice.

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