Skip to main content
Glama
Sign In

SwapChan

by io.github.TSavo
OverviewDiscussionsAdmin

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

taproot_multisig_address
Read-onlyIdempotent

Bitcoin Taproot script-path m-of-n multisig: one CHECKSIGADD leaf under the BIP341 NUMS internal key (no key path), from x-only or compressed PUBLIC keys + threshold + network (bitcoin default, testnet, signet, regtest). Returns address, leaf_script, control_block, merkle_root, internal_key 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": "taproot_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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description still adds genuinely useful context, including offline/pure computation and the fact that no key path exists, but it does not address failure behavior, such as what happens when threshold exceeds the number of pubkeys.

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 first two sentences are dense, front-loaded, and earn their place by carrying the spec and return fields. The final sentence about swapchan_playbook workflows is boilerplate that is irrelevant to a Taproot address-derivation tool and dilutes an otherwise tight definition.

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

Completeness3/5

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

With annotations covering the safety profile and the description listing all six return fields, an agent can call this correctly. The remaining gap is sibling disambiguation: nothing explains why an agent would pick this instead of multisig_address or create_address.

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 33%, so the description compensates well: it says pubkeys may be x-only or compressed, that they form an ordered set, and that the network defaults to bitcoin and accepts testnet, signet, or regtest. Threshold is only implied through the m-of-n framing and could be sharper.

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?

States a specific verb and resource with real technical substance: it builds a Taproot script-path m-of-n multisig address using one CHECKSIGADD leaf under the BIP341 NUMS internal key. That phrasing implicitly separates it from the generic multisig_address sibling, but it never names that sibling or explains the difference explicitly.

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

Usage Guidelines2/5

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

It says the tool is pure offline computation (blocktools) and that nothing is fetched or stored, which clarifies the setting, but there is no explicit when-to-use or when-not guidance versus multisig_address, create_address, or xpub_addresses. The closing pointer to swapchan_playbook lists unrelated swap/rebalance workflows that do not help an agent choose this tool for address derivation.

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