Skip to main content
Glama
chia-mcp

chia-mcp

Official
by Chia-Network

get_all_mempool_tx_ids

Read-only

Retrieve all transaction IDs currently pending in the Chia mempool as spend bundle hashes, providing a lightweight way to list pending transactions without fetching full mempool items.

Instructions

List all transaction IDs currently in the mempool. Returns an array of spend bundle hashes for all pending transactions. Lighter than get_all_mempool_items.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, so the safety profile is covered. The description adds value beyond them by disclosing the return shape (array of spend bundle hashes) and the relative cost versus the items endpoint, which is the main behavioral tradeoff an agent needs.

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 the purpose, then the return value, then the sibling contrast. No filler or redundant restatement of the tool name.

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 parameters and no output schema, the description carries the full burden and covers it: what is listed, what the array contains, and why to pick this over the richer endpoint. Nothing needed 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters and the schema is an empty object, so there is nothing to disambiguate; baseline of 4 applies. The description correctly avoids inventing filtering options.

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?

Specific verb and resource ("List all transaction IDs currently in the mempool"), plus the return contents (spend bundle hashes for pending transactions) and an explicit contrast with the heavier sibling get_all_mempool_items. An agent can distinguish this from get_all_mempool_items without opening either schema.

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?

"Lighter than get_all_mempool_items" gives a concrete selection criterion against the most likely alternative, implying use this when only IDs are needed. It stops short of an explicit when-to-use/when-not statement or naming get_mempool_item_by_tx_id as the follow-up for full items.

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