Skip to main content
Glama
chia-mcp

chia-mcp

Official
by Chia-Network

get_block

Read-only

Retrieve a complete Chia block by its 0x-prefixed header hash, returning transactions, proof of space, reward chain data, and all sub-slot proofs without a local node.

Instructions

Get a full Chia block by its header hash. Returns the complete block including transactions, proof of space, reward chain data, and all sub-slot proofs.

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

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

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered and the description correctly stays consistent with a read operation. It adds useful context about what the payload contains (transactions, proof of space, reward chain data, sub-slot proofs), but says nothing about behavior when a hash is unknown or when full block data is unavailable, and gives no sense of payload size or cost.

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?

Two short sentences, zero filler, with the core action and lookup key front-loaded before the return-content detail. Every clause contributes information.

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?

With no output schema, the description carries the burden of describing the return value; it names the major components but not the structure, and omits failure modes such as an unknown or unavailable block hash. For a single-parameter read tool this is adequate but leaves real gaps.

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%: the single header_hash parameter already documents the 0x-prefixed 32-byte hex format and pattern. The description only restates that lookup is by header hash, adding no format or validity detail beyond the schema, 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?

States a specific verb and resource ("Get a full Chia block") plus the lookup key ("by its header hash"). The word "full" and the enumeration of returned contents (transactions, proof of space, reward chain data, sub-slot proofs) implicitly separate it from record-level siblings like get_block_record, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context by requiring a header hash, but never states when to pick this over get_block_record, get_block_record_by_height, get_blocks, or summarize_block. An agent facing a block-height query or a request for a lightweight record gets no routing guidance.

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