Skip to main content
Glama
teamssUTXO

Bitcoin-MCP-Server

get_bitcoin_transaction_infos

Retrieve comprehensive Bitcoin transaction details including status, amount, fees, fee rate, size, inputs, outputs, and block information by providing a transaction ID.

Instructions

Use this to get comprehensive information about a specific Bitcoin transaction using its transaction ID (txid).

Returns detailed metrics in string format across four categories:

**Transaction Status:**
- Current status (Confirmed/Unconfirmed with visual indicator)
- Transaction date and time

**Economics & Flow:**
- Total amount transferred in BTC
- Transaction fees paid in BTC
- Fee rate in sat/vB (satoshis per virtual byte)

**Technical Structure:**
- Transaction size in bytes
- Number of inputs (sources of funds)
- Number of outputs (destinations)

**Block Information (if confirmed):**
- Block height where transaction was included
- Block hash containing the transaction

The txid is a unique 64-character hexadecimal identifier for each Bitcoin transaction.

Use cases: When you need to verify a payment, check transaction status, analyze fees paid, or investigate transaction details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
txidYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations exist, so the description carries full burden. It details the return categories (status, economics, structure, block info) and notes that block info is conditional on confirmation. It is clear this is a read-only operation.

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 well-structured with clear categories, front-loaded with the purpose, and every sentence adds value without being verbose.

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 the presence of an output schema, the description sufficiently covers input, high-level output categories, and use cases, making it contextually complete for an agent to select and invoke the tool.

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?

The schema has 0% coverage for parameter descriptions, but the description compensates by explaining that txid is a 64-character hexadecimal identifier, adding necessary context beyond the schema.

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 it retrieves comprehensive information about a specific Bitcoin transaction by txid. It distinguishes itself from sibling tools (e.g., block, address, market tools) by focusing on a single transaction.

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 lists explicit use cases (verify payment, check status, analyze fees, investigate details), but does not provide direct comparisons to alternative siblings like get_transaction_input_output or what situations to avoid.

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