Skip to main content
Glama
chia-mcp

chia-mcp

Official
by Chia-Network

get_mempool_items_by_coin_name

Read-only

Retrieves all mempool items that spend or create a specified coin, helping you check whether that coin is involved in any pending transactions.

Instructions

Get all mempool items that reference a specific coin (either spending it or creating it). Useful for checking if a coin is involved in any pending transactions.

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": {
      "coin_name": "<coin_name>"
    },
    "name": "get_mempool_items_by_coin_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
coin_nameYesThe coin ID / name to search for in the mempool (0x-prefixed, 32 bytes hex)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description adds real value by disclosing the matching semantics: it returns items that either spend the coin or create it. It does not cover return shape, ordering, or empty-result behavior.

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?

Two compact sentences: the operation comes first, then the practical use case. No wasted wording, though front-loading the spend/create semantics could be slightly tighter.

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 single-parameter read-only query this is nearly sufficient: purpose, matched-item semantics, and a use case are all present. The only gap is that with no output schema, the description does not hint at what a mempool item record contains.

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 coverage is 100% and the schema already documents the required coin_name as a 0x-prefixed 32-byte hex coin ID. The description only restates 'specific coin' without adding format or filtering nuance beyond the schema.

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?

States a specific verb and resource ('Get all mempool items that reference a specific coin') and clarifies the scope as coin-centric rather than the whole mempool. It is clearly distinguishable from get_all_mempool_items or get_mempool_item_by_tx_id by scope, though it does not name those siblings explicitly.

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?

The sentence 'Useful for checking if a coin is involved in any pending transactions' implies the usage scenario but gives no explicit when-not guidance or alternatives such as looking up by tx id or listing all mempool items.

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