Skip to main content
Glama
teamssUTXO

Bitcoin-MCP-Server

get_transaction_input_output

Analyze a Bitcoin transaction's inputs and outputs to trace fund flow, identify sender and recipient addresses, and review UTXO structure.

Instructions

Use this to get detailed input and output breakdown of a Bitcoin transaction, including all addresses and amounts involved.

Returns comprehensive flow analysis in string format across four sections:

**Accounting Summary:**
- Total incoming volume (sum of all inputs) in BTC
- Total outgoing volume (sum of all outputs) in BTC
- Network fees paid (difference between inputs and outputs) in BTC

**Detailed UTXO Flow:**
- List of all incoming movements (inputs) with:
  - Source address
  - Amount in BTC
  - Previous transaction reference (prev_out)
- List of all outgoing movements (outputs) with:
  - Destination address
  - Amount in BTC
  - Output index

**Participant Registry:**
- Complete list of sender addresses (count included)
- Complete list of recipient addresses (count included)

This provides full transparency into the transaction's inputs (where funds came from) and outputs (where funds went), essential for tracking fund flow and identifying all parties involved.

Use cases: When you need to trace Bitcoin flow, identify sender/recipient addresses, analyze UTXO structure, or investigate complex multi-party transactions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
txidYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations are provided, so the description carries full burden. It thoroughly discloses behavioral traits: returns a comprehensive flow analysis in a structured string format with four sections (Accounting Summary, Detailed UTXO Flow, Participant Registry). No contradictions exist.

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?

The description is relatively long but well-structured with clear sections and bullet points. It front-loads the core purpose and then provides detailed output breakdown. Every sentence adds value, though some redundancy exists.

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?

Despite no annotations and a single parameter, the description is highly complete. It explains the purpose, when to use, the exact output format (four sections with field details), and addresses complexity of multi-party transactions. No gaps remain.

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?

Schema coverage is 0%, but the single parameter 'txid' is implicitly explained by the context (Bitcoin transaction ID). The description does not explicitly define it, but the use cases and output details make its meaning clear. A direct mention would improve it.

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's purpose: 'get detailed input and output breakdown of a Bitcoin transaction, including all addresses and amounts involved.' It uses a specific verb-resource combination and distinguishes from sibling tools like 'get_bitcoin_transaction_infos' by focusing on flow analysis and UTXO details.

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 includes a dedicated 'Use cases' section that lists scenarios (trace Bitcoin flow, identify addresses, analyze UTXO structure, investigate multi-party transactions). It does not explicitly mention when not to use it or name alternatives, 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.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/teamssUTXO/bitcoin_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server