Skip to main content
Glama
chia-mcp

chia-mcp

Official
by Chia-Network

get_mempool_item_by_tx_id

Read-only

Look up a pending Chia transaction in the mempool by its 0x-prefixed transaction ID to inspect the spend bundle, fee, cost, and related metadata.

Instructions

Get a specific mempool item by its transaction ID. Returns the spend bundle, fee, cost, and other mempool metadata for a pending transaction.

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": {
      "tx_id": "<tx_id>"
    },
    "name": "get_mempool_item_by_tx_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
tx_idYesThe transaction ID (spend bundle hash, 0x-prefixed, 32 bytes hex)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.6/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 non-mutating lookup, so the description's marginal duty is small. It does add useful payload context (spend bundle, fee, cost, mempool metadata), but says nothing about what happens if the tx_id is unknown or the transaction has already left the mempool. No contradiction with annotations.

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 tight sentences: the operation and its scoping key come first, followed by the return contents. Nothing is repeated from the schema and there is no filler.

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 one-parameter read tool with a readOnly annotation and full schema coverage, the definition supplies what an agent needs to select and call it, and even summarizes the response fields in the absence of an output schema. The only real gap is undefined behavior for a missing or already-confirmed transaction.

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%, and the single tx_id parameter is fully specified in the schema, including the 0x-prefixed 32-byte hex pattern. The description adds no syntactic or semantic detail beyond that, so the baseline of 3 applies.

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?

"Get a specific mempool item by its transaction ID" states a concrete verb, resource, and retrieval key, which separates it in intent from list-style siblings like get_all_mempool_items or get_mempool_items_by_coin_name. The second sentence names the payload returned. It stops short of explicitly naming a sibling it is not, so it lands at 4 rather than 5.

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?

Usage is only implied: an agent can infer this is the tool for a single pending transaction when the tx_id is known. There is no explicit when-to-use, no statement of when to prefer the coin-name or all-items variants, and no prerequisite or failure-mode guidance.

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