Skip to main content
Glama
chia-mcp

chia-mcp

Official
by Chia-Network

get_network_space

Read-only

Estimate total Chia network storage between two blocks by supplying newer and older header hashes; returns netspace in bytes for comparing network space over time.

Instructions

Estimate the total network space (storage) between two blocks. Returns the estimated netspace in bytes. Provide header hashes of a newer and older block. To obtain header hashes, first call get_block_record_by_height for each height, then use the returned header_hash values.

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": {
      "newer_block_header_hash": "<newer_block_header_hash>",
      "older_block_header_hash": "<older_block_header_hash>"
    },
    "name": "get_network_space"
  }
}

Input Schema

NameRequiredDescriptionDefault
newer_block_header_hashYesHeader hash of the newer (more recent) block (0x-prefixed, 32 bytes hex)
older_block_header_hashYesHeader hash of the older block (0x-prefixed, 32 bytes hex)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds value beyond that by disclosing the return payload (estimated netspace in bytes) and the two-block dependency requirement, which the schema cannot express. It only lightly signals that the value is an estimate, with no note on accuracy or block-range constraints.

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?

Three short sentences, front-loaded with purpose and return value, followed by the required inputs and how to source them. No redundant restatement of the name or of schema patterns.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read-only computation with no output schema, the description covers what it computes, the return unit, and the exact upstream calls needed. Nothing an agent needs in order to call it correctly is missing.

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 coverage is 100% with formatted, pattern-validated descriptions, so the schema already carries the parameter burden. The description adds the meaningful provenance detail that these hashes come from `get_block_record_by_height` and reinforces the newer/older ordering, but offers no extra syntax or edge-case semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — estimate total network space between two blocks — and the unit of the result (bytes). This is clearly distinct from the surrounding block/coin lookup siblings, so an agent can tell it computes a derived metric rather than fetching a record.

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

Usage Guidelines4/5

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

Explicitly describes the prerequisite chain: call `get_block_record_by_height` for each height and pass the returned `header_hash` values. It doesn't state negative conditions (e.g., what happens if hashes are from the same or inverted heights), but the positive usage path is unambiguous.

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