Skip to main content
Glama
chia-mcp

chia-mcp

Official
by Chia-Network

get_all_mempool_items

Read-only

Retrieves every transaction currently in the Chia mempool with full details. For large responses, query transaction IDs first and fetch individual items as needed.

Instructions

Get all items currently in the mempool with full details. WARNING: Can return very large responses (10+ MB on mainnet). Consider using get_all_mempool_tx_ids first to get transaction IDs, then fetch individual items with get_mempool_item_by_tx_id.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries the behavioral burden and does add real value: the large-response warning and the suggested two-step alternative are operational facts not derivable from structured fields. It stops short of describing the item structure or whether the snapshot is consistent, which keeps it from a 5.

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?

Two sentences, front-loaded with purpose and the risk warning in caps, followed immediately by the recommended alternative. No filler or duplicated schema information.

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 tool with no output schema, the description covers what an agent needs to avoid a harmful invocation. The only gap is that "full details" is not elaborated, so the caller must inspect a result to learn the item shape.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. It correctly conveys that no filtering is accepted, implicitly signaling that everything in the mempool comes back.

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 all mempool items) with a scope qualifier ("with full details") and explicitly names the two sibling tools that serve narrower needs, so an agent can pick among them without opening a schema.

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

Usage Guidelines5/5

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

Gives explicit when-not guidance (10+ MB responses on mainnet) and a concrete alternative workflow: call get_all_mempool_tx_ids first, then get_mempool_item_by_tx_id per item. That is a complete decision path rather than a vague hint.

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