Skip to main content
Glama
chia-mcp

chia-mcp

Official
by Chia-Network

get_blockchain_state

Read-only

Retrieve current Chia blockchain state, including peak height, sync status, difficulty, mempool size, and space estimate, to monitor network health without a local node.

Instructions

Get the current Chia blockchain state including peak height, sync status, difficulty, sub-slot iters, mempool size, and space estimate. 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_blockchain_state"
  }
}

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 that this is a safe read, so the description only needs to add context. It adds the notable fact that the call is parameterless and returns a fixed snapshot, but says nothing about freshness, whether mempool size is live, or how the space estimate relates to get_network_space.

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?

The definition front-loads the action and the field list in a single dense sentence. The trailing "Takes no parameters" is slightly redundant given the empty input schema, but it is brief enough not to be a real cost.

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?

There is no output schema, so listing the six returned fields is exactly the right compensation, and it makes the tool self-sufficient for a simple no-arg snapshot call. Only the boundary with overlapping siblings like get_network_space is left unaddressed.

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?

With zero parameters, the baseline is 4. The sentence "Takes no parameters" merely restates the empty schema, so the description neither adds nor detracts from parameter meaning.

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 definition names a specific verb and resource ("Get the current Chia blockchain state") and enumerates the returned fields: peak height, sync status, difficulty, sub-slot iters, mempool size, and space estimate. That field list implicitly separates it from point-lookup siblings such as get_block_record or get_all_mempool_items, but 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 Guidelines3/5

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

The description never says when to reach for this snapshot versus get_network_info, get_network_space, or get_block_record, all of which overlap with the fields it lists. Usage is only implied by the phrase "current ... state", which suggests summary/dashboard polling rather than targeted queries.

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