Skip to main content
Glama
jan3dev

Agentic AQUA

by jan3dev

sideswap_peg_out

Initiate a peg-out to convert L-BTC to BTC. Send L-BTC from a Liquid wallet and receive BTC at your Bitcoin address after confirmations.

Instructions

Initiate a SideSwap peg-out (L-BTC → BTC) and broadcast the L-BTC send. After 2 Liquid confirmations (~2 min) and the federation BTC sweep (typically 15–60 min total), BTC arrives at the user's Bitcoin address. Fees: 0.1% + Bitcoin network fee. Standard way to move L-BTC back to Bitcoin mainchain.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYesAmount in Satoshis to peg out
passwordNoPassword to decrypt mnemonic (if encrypted at rest)
btc_addressYesDestination Bitcoin address (bc1...)
wallet_nameYesLiquid wallet to send L-BTC from
Behavior2/5

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

No annotations provided; description mentions timing and fees but does not disclose error states, return behavior, auth needs, or side effects beyond the basic process.

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?

Two sentences, efficient but the second sentence could be more streamlined; still concise overall.

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?

Covers the core process and fees but does not specify the immediate return value (e.g., transaction ID), which is needed given no output schema.

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?

Schema coverage is 100% with descriptions; the description adds little beyond schema, such as clarifying amount is in Satoshis and destination address format, but does not meaningfully enhance understanding.

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 initiates a SideSwap peg-out (L-BTC to BTC) and broadcasts the L-BTC send, distinguishing it from peg-in and other swap tools.

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?

Describes the process and fees but does not explicitly state when to use this tool vs alternatives like sideswap_peg_quote or sideswap_peg_status, lacking usage 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/jan3dev/agentic-aqua'

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