Skip to main content
Glama
jan3dev

Agentic AQUA

by jan3dev

sideshift_send

Send Bitcoin or Liquid assets to any supported settlement network using a pre-quoted fixed rate. Deposit is broadcast from the local wallet; Liquid asset IDs are auto-resolved.

Instructions

Send funds out via SideShift. Gets a fixed-rate quote, creates the shift, and broadcasts the deposit from the local wallet. Deposit chain MUST be 'bitcoin' or 'liquid'. Both legs must be in the curated allowlist (USDt on ethereum/tron/bsc/solana/polygon/liquid, or BTC on bitcoin) — mirrors AQUA Flutter's supported pairs. Set SIDESHIFT_ALLOW_ALL_NETWORKS=1 to bypass. A refund address is set automatically (the wallet's own deposit-chain address). For non-L-BTC Liquid assets (e.g. USDt-Liquid), the Liquid asset_id is auto-resolved from deposit_coin against the known asset registry — no need to look it up first. Pass liquid_asset_id only to override the registry. ALWAYS call sideshift_quote first and confirm the price with the user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
passwordNoPassword to decrypt mnemonic (if encrypted)
quote_idNoOptional fixed-rate quote id from a prior sideshift_quote call. Pass this after the user confirms the preview so the shift executes at the same rate they saw — without it, the tool fetches a fresh quote and the rate may have moved.
refund_memoNo
settle_coinYes
settle_memoNoRequired for memo networks (BNB, etc.)
wallet_nameNodefault
deposit_coinYesL-BTC: 'btc' (network='liquid'); BTC: 'btc'; USDt-Liquid: 'usdt'
settle_amountNo
deposit_amountNo
settle_addressYesWhere SideShift sends the converted asset
settle_networkYes
deposit_networkYesChain we sign on
liquid_asset_idNoOptional hex asset id. When omitted and depositing a non-L-BTC Liquid asset, it's auto-resolved from `deposit_coin` against the known Liquid asset registry (USDt, DePix, JPYS, EURx, MEX). Pass explicitly only to override the registry.
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses auto-refund address setting, auto-resolution of Liquid asset IDs, and the overall flow (quote, shift, broadcast). Could add error handling details.

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?

Multiple sentences but each adds unique info. Could be slightly tighter, but front-loaded and well-structured. No waste.

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?

Given 13 params and no output schema, the description covers key workflow, constraints, and parameter details. Missing return value description, but overall adequate.

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 54%. Description adds meaning for deposit_coin, deposit_network, liquid_asset_id, quote_id, but leaves settle_amount, deposit_amount, settle_coin, settle_network undocumented. Partial value added.

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 the verb ('Send funds out via SideShift') and resource, and distinguishes from sibling tools like sideshift_quote and sideshift_receive by describing the full flow.

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

Usage Guidelines5/5

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

Explicitly instructs to call sideshift_quote first and confirm price, specifies allowed deposit chains (bitcoin/liquid) and allowlist, and mentions the environment variable bypass.

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