Skip to main content
Glama
Sign In

SwapChan

by io.github.TSavo
OverviewDiscussionsAdmin

Bitcoin m-of-n P2WSH multisig address (dev tool)

multisig_address
Read-onlyIdempotent

Bitcoin m-of-n P2WSH multisig (wsh(multi(..)), unsorted) from compressed PUBLIC keys: threshold + pubkeys (hex, order is consensus-significant) + network (bitcoin default, testnet, signet, regtest). Returns address, witness_script and descriptor. 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": {
      "threshold": "<threshold>",
      "pubkeys": "<pubkeys>"
    },
    "name": "multisig_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNo
pubkeysYesPublic keys in order (order is consensus-significant)
thresholdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Goes meaningfully beyond the annotations: 'Pure, offline computation (blocktools); nothing is fetched or stored' discloses that this is a deterministic local computation with no side effects or network dependency. It also discloses the return fields (address, witness_script, descriptor) despite no output schema, and warns that key order is consensus-significant.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose, inputs, and outputs are front-loaded and tight. But the closing sentence promoting swapchan_playbook and its workflow list is filler for a dev derivation tool and does not earn its place in a description this short.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-param dev tool with no output schema, it covers what is needed: the derivation scheme, input constraints, network options, and the three returned fields. It could be richer on validation (e.g. pubkey count vs threshold) but nothing essential to calling it correctly is missing.

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 only 33%, so the description has to carry weight. It adds that pubkeys must be compressed hex, that order matters, that threshold is the m-of-n count, and that network defaults to bitcoin with four valid values — useful glosses beyond the bare schema, though threshold itself gets no explicit semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource (P2WSH Bitcoin m-of-n multisig, wsh(multi(..)), unsorted) up front, which is enough to separate it from taproot_multisig_address, create_address, and solana_address. The verb is implicit ('from compressed PUBLIC keys ... returns address') rather than stated, and no sibling is named explicitly, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: derive an address from public keys for a given network. There is no when-to-use/when-not guidance versus taproot_multisig_address (the closest sibling) or the create_address/address_tool cluster. The appended swapchan_playbook pointer lists generic workflows but does not tell an agent when to pick this tool.

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