Skip to main content
Glama
chia-mcp

chia-mcp

Official
by Chia-Network

summarize_block

Read-only

Get a compact summary of coin movements in a Chia block, including counts, totals, net, unique puzzle hashes, and top senders/receivers, without returning large addition and removal arrays.

Instructions

Get a compact summary of all coin movements in a block. Instead of returning the full (often 1+ MB) additions and removals arrays, returns: additions_count, removals_count, total_added_mojos, total_removed_mojos, net_mojos, unique_puzzle_hashes, and four ranked arrays — top_additions, top_removals, top_receivers, and top_senders (the N largest by amount, controlled by the top_n parameter, default 10). Non-transaction blocks return zero counts since they carry no spends. Much more useful than get_additions_and_removals for understanding what happened in a block without blowing the context window. Accepts either header_hash or height (height resolves to header_hash via get_block_record_by_height).

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": "summarize_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
top_nNoNumber of largest coin movements to include (default 10)
heightNoBlock height. If provided, header_hash is resolved automatically via get_block_record_by_height.
header_hashNoThe header hash of the block (0x-prefixed, 32 bytes hex). Provide this OR height.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, so the description carries the return-shape burden and does it well: it enumerates the exact aggregate fields and four ranked arrays, notes the internal delegation to get_block_record_by_height when height is supplied, and discloses the edge case that non-transaction blocks return zero counts. That is meaningful behavior beyond what the annotation tells an agent.

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?

Front-loaded with the purpose and the size rationale before the field inventory, and every sentence is doing work. The long enumeration of return fields is warranted given no output schema, though the single run-on sentence structure could be split for scannability.

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?

With no output schema, the description fully compensates by documenting the returned aggregates and ranked arrays, plus the zero-count behavior for non-transaction blocks. All three optional params are addressed and the internal resolution step is disclosed, leaving nothing an agent needs in order to call it correctly.

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?

Schema coverage is 100%, so a baseline of 3 applies, and the description earns above that by explaining what top_n actually controls (the size of the four ranked arrays, default 10) and by restating the height-to-header_hash resolution path. It adds modest value rather than new syntax or constraints beyond the schema.

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 ("Get a compact summary of all coin movements in a block") and immediately contrasts it with the sibling get_additions_and_removals, so an agent can distinguish the two without opening a schema. The scope (aggregate counts and ranked top-N arrays rather than full arrays) is concrete.

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 names the alternative and the reason to prefer this tool (avoiding a 1+ MB payload that blows the context window). It does not spell out the reverse condition — when an agent should use get_additions_and_removals instead (i.e., when full per-coin detail is actually needed) — which leaves that half of the decision implicit.

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