Skip to main content
Glama
chia-mcp

chia-mcp

Official
by Chia-Network

get_block_spends_with_conditions

Read-only

Retrieves every coin spend in a Chia block and parses its CLVM conditions, returning puzzles, solutions, and outputs such as CREATE_COIN and AGG_SIG for inspection.

Instructions

Get all coin spends in a block with their parsed CLVM conditions. Returns puzzles, solutions, and the conditions each spend produced (CREATE_COIN, AGG_SIG, etc.).

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

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.2/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, and the description usefully extends that by describing what the response actually contains (puzzles, solutions, per-spend conditions with concrete condition names). It says nothing about behavior for unknown block hashes, result size, or ordering, which matter for a block-scoped dump that could be large.

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 tight, front-loaded sentences with no filler. The second sentence partly restates the first's mention of conditions, a minor redundancy, but the added puzzle/solution and example condition names earn their space.

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?

With no output schema, the description does its job by enumerating the return shape and giving example condition types, and the annotations cover the safety profile. Remaining gaps (error behavior, ordering, size) are modest for a single-parameter read tool.

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% for the single header_hash parameter, including the 0x-prefixed 32-byte pattern, so the schema carries the load. The description never mentions the parameter or its format, adding nothing beyond the structured field.

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 all coin spends in a block') plus the distinguishing payload ('parsed CLVM conditions'). The mention of puzzles, solutions, and condition types implicitly separates it from the plainer get_block_spends sibling, 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?

There is no when-to-use guidance, no mention of when to prefer get_block_spends or get_puzzle_and_solution_with_conditions instead, and no prerequisites or cost warnings. The agent must infer the selection rule from the return-value description alone.

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