Skip to main content
Glama

Create a deposit order

create_deposit_order

Creates a one-time deposit order; you pay from your own wallet. Returns the deposit address (or Lightning invoice), the exact amount to send (also in base units with the token decimals), any required memo, the expiry and the rozoPaymentId. This server holds no keys and sends nothing. Send exactly the amount, on exactly that chain and token, before expiresAt. An unfunded order simply expires at no cost. For a native coin the result also carries quoteExpiresAt (the end of the price lock, which expiresAt equals): send the exact coin amount before it. For TRON or TON the result carries the receiving address, the exact amount, the TON comment when one is required, the fees and expiresAt, and no rozoPaymentId: track it with payment_status and the url. Native coins (ETH on Ethereum, Base, Arbitrum; BNB on BNB Chain; POL on Polygon; SOL on Solana) are exact-out like Lightning: the order states the exact coin amount, priced at the current rate plus an FX spread on top of the service fee, and that price holds only until quoteExpiresAt. Native ETH, BNB and SOL take OpenRouter invoices of up to 10,000 credits (about $10,500; refused only above $12750 of callerPays, service fee included, so a 10,000-credit invoice always fits). POL is capped at $3500 (native ETH on Ethereum needs at least $1), and a native coin is offered only when quote_invoice lists it for that invoice. ZEC on Zcash is not available through this server: send a payer holding ZEC to https://checkout.rozo.ai/zec. On-chain BTC (the Bitcoin network, Beta) is not available through this server either; the lightning chain id here is Bitcoin Lightning only. Send a payer who wants to pay on-chain to https://checkout.rozo.ai/btc-onchain. USDT and TRX on TRON (Beta) and USDT on TON go through a dedicated route (route "tron_ton_alpha", the same backend as checkout.rozo.ai/tron and /ton): create_deposit_order returns one exact amount, a receiving address and, on TON when required, a six digit comment, valid until expiresAt. TRON Beta charges 1% with a $0.30 minimum; TON charges 1%; the exact fees come with the order. These orders have no rozoPaymentId: check them with payment_status and the payment link url. Availability can change; quote_invoice reports whether TRON and TON are open for a given invoice.

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": {
      "url": "<url>",
      "chainId": "<chainId>",
      "tokenSymbol": "<tokenSymbol>"
    },
    "name": "create_deposit_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPayment link: https://payments.coinbase.com/payment-links/pl_... or https://payments.coinbase.com/payment-sessions/paymentSession_...
emailNoOptional contact email so ROZO can reach the payer if the payment needs attention. Ask the user once if they are present; never required, omit it if they decline.
chainIdYesSource chain id from supported_coins: "1" Ethereum, "56" BNB Chain, "137" Polygon, "42161" Arbitrum, "900" Solana, "8453" Base, "1500" Stellar, "lightning", "728126428" TRON (Beta), "1600" TON.
tokenSymbolYesToken you will pay with: USDC, USDT, BTC (Lightning), the chain native coin ETH (1, 8453, 42161), BNB (56), POL (137), SOL (900), or USDT / TRX on TRON, USDT on TON.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / chainId / description
      Previous value: -"Source chain id from supported_coins: \"1\" Ethereum, \"56\" BNB Chain, \"137\" Polygon, \"42161\" Arbitrum, \"900\" Solana, \"8453\" Base, \"1500\" Stellar, \"lightning\"."New value: +"Source chain id from supported_coins: \"1\" Ethereum, \"56\" BNB Chain, \"137\" Polygon, \"42161\" Arbitrum, \"900\" Solana, \"8453\" Base, \"1500\" Stellar, \"lightning\", \"728126428\" TRON (Beta), \"1600\" TON."
    • changedInput schema / properties / chainId / enum
      Previous value: -[
      -  "1",
      -  "56",
      -  "137",
      -  "900",
      -  "1500",
      -  "8453",
      -  "42161",
      -  "lightning"
      -]New value: +[
      +  "1",
      +  "56",
      +  "137",
      +  "900",
      +  "1500",
      +  "1600",
      +  "8453",
      +  "42161",
      +  "728126428",
      +  "lightning"
      +]
    • changedInput schema / properties / tokenSymbol / description
      Previous value: -"Token you will pay with: USDC, USDT, BTC (Lightning), or the chain native coin ETH (1, 8453, 42161), BNB (56), POL (137), SOL (900)."New value: +"Token you will pay with: USDC, USDT, BTC (Lightning), the chain native coin ETH (1, 8453, 42161), BNB (56), POL (137), SOL (900), or USDT / TRX on TRON, USDT on TON."
  2. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"Coinbase link: https://payments.coinbase.com/payment-links/pl_... or https://payments.coinbase.com/payment-sessions/paymentSession_..."New value: +"Payment link: https://payments.coinbase.com/payment-links/pl_... or https://payments.coinbase.com/payment-sessions/paymentSession_..."
  3. Changed3 schema fields changed
    • changedInput schema / properties / chainId / description
      Previous value: -"Source chain id from supported_coins, e.g. \"900\" (Solana), \"8453\" (Base), \"lightning\"."New value: +"Source chain id from supported_coins: \"1\" Ethereum, \"56\" BNB Chain, \"137\" Polygon, \"42161\" Arbitrum, \"900\" Solana, \"8453\" Base, \"1500\" Stellar, \"lightning\"."
    • changedInput schema / properties / chainId / enum
      Previous value: -[
      -  "1",
      -  "56",
      -  "137",
      -  "900",
      -  "1500",
      -  "8453",
      -  "lightning"
      -]New value: +[
      +  "1",
      +  "56",
      +  "137",
      +  "900",
      +  "1500",
      +  "8453",
      +  "42161",
      +  "lightning"
      +]
    • changedInput schema / properties / tokenSymbol / description
      Previous value: -"Token you will pay with, e.g. USDC, USDT, BTC."New value: +"Token you will pay with: USDC, USDT, BTC (Lightning), or the chain native coin ETH (1, 8453, 42161), BNB (56), POL (137), SOL (900)."
  4. Changed1 schema field changed
    • addedInput schema / properties / email
      Added value: +{
      +  "description": "Optional contact email so ROZO can reach the payer if the payment needs attention. Ask the user once if they are present; never required, omit it if they decline.",
      +  "maxLength": 320,
      +  "type": "string"
      +}
  5. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, it discloses that the server holds no keys and sends nothing, that unfunded orders expire at no cost, and that the caller must send exactly the specified amount before expiresAt. It also explains route-specific behavior, fees, caps, and which orders lack a rozoPaymentId.

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

Conciseness3/5

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

The description is front-loaded with purpose and key safety information, but it is very long and repeats certain details, such as the absence of rozoPaymentId for TRON/TON orders and the tracking path via payment_status. Much of the route-specific detail is useful, yet the structure could be tightened.

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 complex multi-chain payment-order tool with no output schema, the description is highly complete: it explains what is returned, how to fund the order, expiry behavior, fee and cap constraints, and unsupported chains. It gives the agent enough information to create and correctly instruct the payer without needing to infer critical behavior.

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 description coverage is 100%, so the schema already defines all four parameters, including the url format, email purpose, chainId enum meanings, and supported tokenSymbol values. The description adds some behavioral constraints on native coins and availability, but it does not add meaningful parameter-level semantics for url or email beyond the 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?

The first sentence states a specific verb and resource: 'Creates a one-time deposit order; you pay from your own wallet.' The description also differentiates this operation from sibling tools by pointing to payment_status for tracking and quote_invoice for availability.

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?

It clearly defines when to use this tool and when not to: ZEC and on-chain BTC payers are redirected to external checkout URLs, while TRON and TON go through a dedicated route. It also tells the agent to use quote_invoice to check availability and payment_status to track orders without a rozoPaymentId.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.