Skip to main content
Glama
Sign In
Agentic AQUA

Agentic AQUA

Official
by AquaWallet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

changelly_receive

Creates a Changelly variable-rate deposit address on the source USDt network so an external sender can pay and settle USDt-Liquid to your wallet; returns a scannable QR code.

Instructions

Receive USDt-Liquid via a Changelly variable-rate swap. Returns a deposit address on the source chain — the external sender pays to it. Settles to the wallet's Liquid address as USDt-Liquid. STRONGLY RECOMMEND passing external_refund_address. Also returns qr_code_path: a PNG QR of the deposit address — display it to the user so they can scan it.

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>"
    },
    "name": "changelly_receive"
  }
}

Input Schema

NameRequiredDescriptionDefault
amount_toNoAmount to receive in the wallet (decimal string). Mutually exclusive with amount_from.
amount_fromNoAmount the external sender will deposit (decimal string, e.g. '50'). Mutually exclusive with amount_to.
wallet_nameNodefault
external_networkYesSource USDt network the external sender pays from
external_refund_addressNoSource-chain refund address (strongly recommended)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses the variable-rate swap, deposit address generation, and QR output. However, missing details on swap expiration, rate lock, slippage, or consequences of omitting the refund address. Basic behavior is covered but lacks depth.

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?

The description is concise, front-loading the main purpose and key output. It uses clear sentences with no wasted words. Slightly longer than necessary, but still efficient.

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 basic flow and outputs (deposit address, QR code) despite no output schema. However, missing details on swap lifecycle (timeouts, failures), amount constraints, and error handling. Adequate but has gaps for a tool with 5 parameters and no annotations.

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 high (80%), so baseline is 3. The description adds minimal value beyond the schema, only strongly recommending external_refund_address. No explanation of amount_to/amount_from mutual exclusivity or enum values, so it meets the minimum.

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 tool receives USDt-Liquid via a Changelly variable-rate swap, specifying the returned deposit address and settlement to wallet's Liquid address. It distinguishes from sibling tools like changelly_send and sideshift_receive by naming the specific asset and provider.

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?

Provides clear context: the external sender pays the deposit address, and strongly recommends external_refund_address. However, it does not explicitly mention when not to use (e.g., for fixed-rate swaps) or list alternatives, though the flow is well-described.

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