Skip to main content
Glama
Sign In

Mempool Space

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Tx Status

get_tx_status
Read-onlyIdempotent

Return confirmation status (confirmed, block hash, block height) for a txid without fetching the full transaction body.

Input Schema

NameRequiredDescriptionDefault
txidYes
networkNoWhich Bitcoin network. Defaults to mainnet — the real Bitcoin network, which is what "Bitcoin" means in an ordinary question. "bitcoin" and "btc" are accepted as aliases for mainnet.mainnet

Output Schema

NameRequiredDescriptionDefault
confirmedNoIs transaction confirmed
block_hashNoConfirmation block hash
block_timeNoConfirmation block timestamp
block_heightNoConfirmation block height

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / network / default
      Added value: +"mainnet"
    • addedInput schema / properties / network / description
      Added value: +"Which Bitcoin network. Defaults to mainnet — the real Bitcoin network, which is what \"Bitcoin\" means in an ordinary question. \"bitcoin\" and \"btc\" are accepted as aliases for mainnet."
    • addedInput schema / properties / network / enum
      Added value: +[
+  "mainnet",
+  "testnet",
+  "signet",
+  "liquid"
+]
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds the specific return fields (confirmed, block hash, block height), which is useful but not extensive.

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?

The description is a single, well-structured sentence that front-loads the key purpose and return details. No unnecessary words.

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?

The tool has an output schema (not shown but present), so the description doesn't need to detail return values. However, it might benefit from mentioning error states or txid format, but given simplicity, it is reasonably complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

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

Schema coverage is 50% (network has a description, txid does not). The tool description does not compensate by describing txid format or constraints. It only mentions 'txid' in the return context, not the input parameter specifics.

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?

The description clearly states the tool returns confirmation status (confirmed, block hash, block height) for a given txid, emphasizing that it avoids fetching the full transaction body. This distinguishes it from siblings like get_transaction, which would return the full body.

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?

The description implicitly tells when to use this tool: when only confirmation status is needed and the full transaction body is unnecessary. It does not explicitly mention alternatives or when not to use, but the context is clear.

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

All Mempool Space toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources