Skip to main content
Glama
jan3dev

Agentic AQUA

by jan3dev

wapupay_create_order

Create a WapuPay order to obtain a Liquid USDT funding address for paying Argentine pesos via bank alias. Returns funding details, expiry, and a QR code.

Instructions

Create a WapuPay order and get a Liquid USDT funding address. Creates the tentative (freezing the quote) and issues funding instructions. Returns address_destination (Liquid), asset_id (USDT), funding_amount_usdt, total_amount_usdt, total_funding_amount_base_units, funding_expires_at and a QR. Pay the TOTAL with lw_send_asset (amount = total_funding_amount_base_units); WapuPay then makes a P2P payer settle ARS to the bank account. Does NOT broadcast the payment itself — confirm the quote with the user first via wapupay_quote.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoTransfer speed. 'fast_fiat_transfer' name it 'Fast Transfer' for the user (default, higher fee): prioritized, completes in ~10 min to 1 hour during daytime (not instant). 'fiat_transfer' name it 'Normal Transfer' for the user (standard, lower fee): takes 3 to 12 hours; recommend only when there is no rush, or when paying at night/weekends since usually a payer picks it up the next day. Explain this trade-off to the user.fast_fiat_transfer
aliasYesRecipient bank alias / CBU / CVU
amount_arsYesAmount in Argentine pesos (decimal string, e.g. '10000')
wallet_nameNoWallet you intend to fund from (recorded for tracking)default
receiver_nameNoRecipient name (optional)
refund_addressNoLiquid mainnet refund address (lq1…/ex1…) if funding cannot execute (optional); validated before the order is created
Behavior5/5

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

Fully discloses behavior: creates tentative order, issues funding instructions, returns specific fields, and emphasizes it does NOT broadcast payment. No annotations to contradict.

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?

Informative but slightly long; every sentence adds value. Front-loaded with main purpose. Could be tighter, but no redundancy.

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

Completeness5/5

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

For a tool with 6 params, no output schema, and no annotations, the description covers all key aspects: inputs, outputs, flow, and relationship to sibling tools. Completely sufficient for an AI agent.

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 100%, but description adds meaningful context for 'type' enum (explains trade-off between fast and normal) and mentions refund_address validation. Adds value beyond schema.

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?

Clearly states it creates a WapuPay order and gets a Liquid USDT funding address. Distinguishes from siblings by noting it does not broadcast the payment and that users should confirm with wapupay_quote first.

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 explains when to use (after quote) and when not to (does not broadcast payment). Provides alternative tool (lw_send_asset) for payment and advises confirming quote via wapupay_quote.

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