Skip to main content
Glama
chia-mcp

chia-mcp

Official
by Chia-Network

get_block_count_metrics

Read-only

Retrieve compact block, uncompact block, and hint counts to monitor Chia chain health and track compactification progress.

Instructions

Get block count metrics: compact_blocks, uncompact_blocks, and hint_count. Useful for monitoring chain health and compactification progress. 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_block_count_metrics"
  }
}

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?

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds that the tool takes no parameters and that the counts relate to chain health/compactification progress, but it does not say whether counts are cumulative-since-genesis or point-in-time, nor whether the call can be expensive on a large chain.

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?

Two short sentences, front-loaded with the returned field names before the use case. Every sentence earns its place, though 'Takes no parameters' restates what the empty schema already shows, which is a minor waste.

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 zero-parameter read-only tool with no output schema, the description supplies the field names the caller will receive and the interpretive context (chain health, compactification progress), which is enough to call it correctly. It would be stronger if it noted whether values are integers or reset on restart.

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, and the explicit statement 'Takes no parameters' removes any doubt about whether block-height or range filters exist. It is mildly redundant against the empty schema but confirms the zero-argument contract.

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 names a specific verb (Get) and a specific resource (block count metrics), then enumerates the exact fields returned: compact_blocks, uncompact_blocks, hint_count. That is far more precise than the sibling tools (get_block, get_block_records, get_block_spends), which all deal with block content rather than aggregate metrics, though the description never explicitly contrasts 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 'Useful for monitoring chain health and compactification progress' gives a real use context, which is more than most getters offer. However, it does not say when to prefer this over get_blockchain_state or get_block, nor does it set any preconditions or exclusions, so the agent must infer the boundary.

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