Skip to main content
Glama
chia-mcp

chia-mcp

Official
by Chia-Network

get_unfinished_block_headers

Read-only

Retrieves all unfinished block headers—blocks started but not yet completed by the timelord—so you can inspect pending block progress. Takes no parameters.

Instructions

Get all unfinished block headers. These are blocks that have been started but not yet completed by the timelord. Takes no parameters.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_unfinished_block_headers"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

The readOnlyHint annotation already establishes the safety profile, and the description adds that the tool returns ALL such headers with no filtering. It does not disclose ordering, expected result size, or whether unfinished headers can disappear mid-query — modest added value beyond annotations.

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 the purpose followed by the definition and invocation note. Nothing is wasted, though the closing parameter note restates what the empty schema already shows.

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 no-parameter, read-only listing tool with no output schema, the description covers what is needed to call it correctly. Return shape and result volume are left unexplained, but annotations and the simple contract keep the gap small.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero parameters, so the baseline is 4. The description confirms 'Takes no parameters,' which is mildly redundant with the empty schema but removes any doubt about how to invoke it.

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+resource ("Get all unfinished block headers") and defines the key term by explaining that these are blocks started but not completed by the timelord. It is distinguishable from siblings like get_block or get_blocks by the 'unfinished' qualifier, though it doesn't explicitly contrast itself with them.

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?

The phrase 'unfinished block headers' is self-selecting enough that an agent can infer when it applies, but there is no explicit when-to-use guidance, no mention of when to prefer get_blocks or get_block_record, and no stated preconditions.

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