Skip to main content
Glama
chia-mcp

chia-mcp

Official
by Chia-Network

get_additions_and_removals

Read-only

List all coins created and spent in a specific Chia block to analyze its full transaction activity. Provide the block header hash to retrieve additions and removals.

Instructions

Get all coins created (additions) and spent (removals) in a specific block. Useful for analyzing all transactions in a block. Requires the block's header hash.

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

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

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

The readOnlyHint annotation already establishes this is a safe read, and the description is consistent with that. It adds no behavioral context beyond the annotations — nothing about response shape, ordering, pagination, or whether large blocks truncate results — so it only meets the lower bar that annotations set.

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?

Three short sentences, front-loaded with the core operation and the definition of additions/removals. The second sentence ("Useful for analyzing all transactions in a block") largely restates what the first already conveys, making it the one mildly redundant element.

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

Completeness3/5

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

For a simple one-parameter read tool with annotations this is mostly sufficient, but there is no output schema and the description does not indicate the return shape — whether additions and removals come back as separate arrays, in what order, or whether results are limited. That leaves a genuine gap for a query 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%: header_hash is documented with format and pattern in the schema, and the description merely restates "Requires the block's header hash." It adds no meaning beyond the schema, so the baseline 3 applies for a single well-documented parameter.

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 states a specific verb and resource — retrieving coins created (additions) and spent (removals) for a single block — and defines both terms, which disambiguates it from the spends-only siblings like get_block_spends. It stops short of explicitly naming those siblings as alternatives, so it is clear but not maximally differentiated.

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?

"Useful for analyzing all transactions in a block" gives a general use context but no explicit when-to-use/when-not or pointer to alternatives such as get_block_spends (removals only) or get_block (header/metadata). Usage is implied rather than prescribed.

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