Skip to main content
Glama
Sign In

Mempool Space

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Transaction

get_transaction
Read-onlyIdempotent

Fetch full transaction detail (inputs, outputs, fee, size, confirmation status) for a given txid on mainnet/testnet/signet/liquid.

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
feeNoTransaction fee in satoshis
vinNoInput array
sizeNoTransaction size in bytes
txidNoTransaction ID
voutNoOutput array
statusNoConfirmation status
weightNoTransaction weight in WU
versionNoTransaction version
locktimeNoLocktime

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

A4.5/5.0
Behavior5/5

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

Annotations already provide readOnlyHint, idempotentHint, openWorldHint, destructiveHint. Description adds actionable detail on return content (inputs, outputs, fee, etc.) and supported networks, exceeding what annotations offer.

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?

Single sentence front-loads purpose and key elements. Every word earns its place; no fluff.

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?

Given output schema exists, description needn't explain return values. Covers all essential input info and what the tool provides. Annotations confirm safe, idempotent behavior. Complete for a transaction fetcher.

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 50% (network param described). Description lists networks but adds no new semantics for txid or beyond schema. Minimal added value over structured data.

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?

Description clearly states verb (Fetch), resource (transaction detail), and specific data fields (inputs, outputs, fee, size, confirmation status). Lists supported networks, distinguishing from siblings like get_tx_status.

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?

Specifies required input (txid) and optional network. Implicitly differentiates from get_tx_status by focusing on full detail, but lacks explicit when-not-to-use guidance.

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