Skip to main content
Glama
Sign In
Agentic AQUA

Agentic AQUA

Official
by AquaWallet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

changelly_send

Sends USDt-Liquid to an external network through a Changelly fixed-rate swap by fetching a quote, creating an order, and broadcasting the wallet deposit; refunds go to the wallet's Liquid address.

Instructions

Send USDt-Liquid out via a Changelly fixed-rate swap. Gets a quote, creates the order, and broadcasts the deposit from the local wallet. Refund address is set automatically (the wallet's own Liquid address). ALWAYS call changelly_quote first and confirm the price with the user.

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": {
      "external_network": "<external_network>",
      "settle_address": "<settle_address>"
    },
    "name": "changelly_send"
  }
}

Input Schema

NameRequiredDescriptionDefault
rate_idNoRate id from a prior changelly_quote call — pass this to lock the previewed rate and avoid drift
passwordNoPassword to decrypt mnemonic (if encrypted at rest)
amount_toNoAmount the recipient should receive (decimal string). Mutually exclusive with amount_from. Use this to pay fees from the sender side, matching AQUA APK behavior.
amount_fromNoUSDt-Liquid to send (decimal string, e.g. '100'). Mutually exclusive with amount_to.
wallet_nameNodefault
password_fileNoPath to a local file containing the wallet password; keeps the password out of the conversation. Do not combine with password.
settle_addressYesExternal chain address to receive USDt at
external_networkYesTarget USDt network

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does reveal the multi-step internal sequence (quote, create order, broadcast deposit) plus the side effect that funds actually leave the local wallet. It also discloses that the refund address is auto-derived from the wallet's own Liquid address, which is real behavioral context an agent could not infer. It omits irreversibility of the broadcast and fee/rate-drift failure behavior, keeping it below a 5.

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

Conciseness5/5

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

Three sentences, front-loaded with the action and the operation's scope, followed by the side-effect note and the prerequisite. No filler or repetition of schema content.

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 an 8-parameter value-moving tool with no annotations and no output schema, the description covers the operation flow, prerequisite, approval requirement, and automatic refund handling. What is missing is return-value expectation (order id, deposit txid) and error paths, which matters somewhat without an 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 88%, so the schema already documents nearly every parameter, including rate_id, amount_to/amount_from exclusivity, and the password_file warning. The description adds only the framing that a quote precedes the call, which loosely explains why rate_id exists, but no new param-level meaning. Baseline 3 applies.

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 with directionality: send USDt-Liquid out via a Changelly fixed-rate swap. The word 'out' implicitly separates it from changelly_receive, so an agent can distinguish the two siblings without opening a schema.

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?

'ALWAYS call changelly_quote first and confirm the price with the user' gives an explicit prerequisite and an approval gate. It stops short of naming when to choose this over the many alternative send paths (sideshift_send, wapupay_fund_order, lw_send, btc_send), so routing between providers is left to inference.

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

Deploy Server

Other Tools