Skip to main content
Glama

combine_btc_psbts

DestructiveIdempotent

Merge multiple multi-sig PSBTs from cosigners into a single signed transaction. Validates all PSBTs share the same unsigned transaction body before combining signatures.

Instructions

Merge 2-15 partial PSBTs from multi-sig cosigners into one whose inputs carry every cosigner's signature. Each entry must be a base64-encoded PSBT v0 sharing the same unsigned tx body (same inputs/outputs/sequences/locktime); only per-cosigner witness data may differ. Refuses with a clear error when bodies disagree — combining across distinct unsigned txs would silently merge signatures across different transactions. Returns the merged PSBT plus a per-input signature count so the caller can tell whether the threshold has been reached. No device touch.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
psbtsYesArray of 2-15 base64-encoded PSBT v0 strings to merge. Every entry must share the same unsigned tx body (same inputs in the same order, same outputs in the same order, same sequence numbers, same locktime); only the per-cosigner witness data may differ. Refused if any pair has a mismatched body — combining PSBTs across distinct unsigned txs would silently merge signatures across different transactions.
Behavior4/5

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

Adds beyond annotations: describes error handling on body mismatch, return of per-input signature count, and 'No device touch' (no hardware interaction). No contradictions with annotations (destructiveHint=true, idempotentHint=true are consistent with merging 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?

Four sentences, front-loaded with core purpose, then constraints, error behavior, and output. No extraneous words. Every sentence earns its place.

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 no output schema, description covers return value (merged PSBT + signature count), error handling, and constraints. Covers all essential aspects for usage.

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?

Single parameter 'psbts' is fully described in schema (100% coverage). Tool description repeats same constraints, adding no new information beyond the schema's description. Baseline 3 for high coverage.

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?

Explicitly states it merges 2-15 partial PSBTs from multi-sig cosigners, with clear constraints on input format (base64 v0, same unsigned tx body). Distinguishes from sibling tools like sign_btc_multisig_psbt and finalize_btc_psbt by focusing on combination step.

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?

Provides clear conditions for use (same unsigned tx body, only witness data differs) and error behavior when violated. Could explicitly mention not to use with PSBTs from different transactions, but the constraints imply this. Alternative tools are identifiable from context.

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/szhygulin/recon-crypto-mcp'

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