Skip to main content
Glama
Sign In

SwapChan

by io.github.TSavo
OverviewDiscussionsAdmin

Combine cosigner PSBTs and finalize (dev tool)

combine_psbts
Read-onlyIdempotent

Merge cosigners' partially signed PSBTs (base64 or hex) for the same transaction and finalize once the threshold is met. Returns signed_tx (hex of the finalized tx, ready for the user's own broadcast) and psbt (base64 of the combined PSBT). Errors: no_psbts, not_a_psbt, psbts_do_not_combine, not_enough_signatures. Signs nothing and broadcasts nothing. Pure, offline computation (blocktools); nothing is fetched or stored. How to combine this with the other tools: swapchan_playbook (workflows: find-money, best-swap, rebalance, revoke-approvals, bridge-stuck, token-safety, recover-old-wallet).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "psbts": "<psbts>"
    },
    "name": "combine_psbts"
  }
}

Input Schema

NameRequiredDescriptionDefault
psbtsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, and the description adds genuinely new behavioral facts: it signs nothing, broadcasts nothing, does no network I/O, stores nothing, and enumerates the four error codes an agent may need to branch on. Missing are ordering requirements or what happens when more than the threshold of PSBTs is supplied.

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?

Purpose, return values, and error codes are front-loaded and each sentence carries weight. The trailing 'how to combine this with the other tools' pointer leans on a boilerplate playbook reference, slightly diluting an otherwise tight definition.

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?

With only one parameter, no output schema, and rich annotations, the description supplies everything an agent needs: what it consumes, what it returns (signed_tx hex and combined psbt base64), the failure modes, and the offline purity guarantee.

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%, so the description must carry the burden—and it does explain the parameter's meaning (cosigners' PSBTs for the same transaction) and accepted encodings (base64 or hex), which the schema omits entirely. It does not mention the 16-item cap or the maxLength constraint, leaving a small gap.

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?

States a specific verb and resource—'Merge cosigners' partially signed PSBTs ... and finalize once the threshold is met'—plus accepted input formats. This is clearly distinguishable from siblings like signing_guide (instructions) and broadcast_tx (broadcasting).

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 establishes the precondition (threshold met) and indirectly routes broadcasting elsewhere via 'ready for the user's own broadcast.' It does not explicitly contrast with signing_guide or build_plan_tx, so the when-not guidance is implied rather than stated.

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

All SwapChan 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