Gate Exchange Collateralloan

Step 1: Classify intent

Identify the user intent using Routing Rules (Cases 1–7). If required inputs are missing (order_id, currency, amount, fixed term), ask clarifying questions before proceeding.

Step 2: Read-only requests (rates, LTV, quota, orders)

Call the corresponding MCP tool when the user asks for rates, LTV, quota, order list, or order detail.

Call cex_mcl_list_user_currency_quota with:

• type: collateral or borrow
• currency: comma-separated (borrow: single currency)

Call cex_mcl_get_multi_collateral_ltv with:

• (no params)

Call cex_mcl_get_multi_collateral_fix_rate with:

• (no params)

Call cex_mcl_get_multi_collateral_current_rate with:

• currencies: comma-separated currency list

Call cex_mcl_list_multi_collateral_orders with:

• page, limit (optional)
• sort (optional): time_desc, ltv_asc, ltv_desc
• order_type (optional): current or fixed

Call cex_mcl_get_multi_collateral_order_detail with:

• order_id

Key data to extract:

• LTV thresholds, fixed/current rates, quota rows, order_id, order status, collateral and borrow details

Step 3: Create loan (current or fixed)

If current loan:

1. Build draft (collateral list + borrow currency/amount).
2. Ask for confirmation.
3. Call cex_mcl_create_multi_collateral with order: JSON string (borrow_currency, borrow_amount, collateral_currencies, order_type: current).

If fixed loan:

1. Call cex_mcl_get_multi_collateral_fix_rate (returns a list); filter by borrow_currency; take rate_7d or rate_30d as fixed_rate (hourly rate; pass through unchanged, do not convert or relabel as annual/daily).
2. Build draft with fixed_type and fixed_rate (describe to user as hourly rate if showing).
3. Ask for confirmation.
4. Call cex_mcl_create_multi_collateral with order: JSON including order_type: fixed, fixed_type 7d/30d, fixed_rate.

Step 4: Repay

Build draft, ask confirmation, then call cex_mcl_repay_multi_collateral_loan with:

• repay_loan: JSON string with order_id and repay_items [{ currency, amount, repaid_all }]

Step 5: Add or redeem collateral

Build draft, ask confirmation, then call cex_mcl_operate_multi_collateral with:

• collateral_adjust: JSON string with order_id, type (append | redeem), collaterals [{ currency, amount }]

Judgment Logic Summary

• Determine case by keywords and required inputs (loan create / repay / add / redeem / list).
• Fixed loan requires fix_rate lookup; if not available, stop and inform user.
• All write operations must be confirmed before calling MCP.
• Auth failure (401/403) prompts API key configuration.

Report Template

When asking for confirmation: Draft:

• Type: {current|fixed|repay|append|redeem}
• Order ID: {order_id if applicable}
• Borrow: {borrow_amount} {borrow_currency}
• Collateral: {collateral_amounts}
• Fixed term/rate: {fixed_type} / {fixed_rate} (hourly rate)

Please confirm to proceed.

On success:

• Summary of action and key identifiers (order_id, amounts).

On failure:

• Error message and next-step guidance (e.g., check currency/amount/LTV).

Prerequisites

• MCP Dependency: Requires gate-mcp to be installed.
• Authentication: Order list, detail, repay, collateral, quota, and records require API key; LTV, fix rate, and current rate are public without key.
• Disclaimer: Loan and LTV information is for reference only and does not constitute investment advice. Understand product terms and liquidation risk before borrowing.

Available MCP Tools

Routing Rules

Execution

1. Identify user intent from the Routing Rules table above.
2. For Cases 1–5: Read the corresponding scenario in references/scenarios.md and follow the Workflow (show order draft, then call MCP only after user confirmation).
3. For Case 6: Call list or detail tool as needed; no confirmation required for read-only. Never show borrow_time, maturity, due date, operate_time, create_time, repay_time, Unix timestamps, or any other time-related fields in the reply—even if the user asks for dates/times; suggest checking the Gate app or web for timing details.
4. For Case 7: Do not expose API keys or raw errors; prompt the user to set up Gate CEX API Key with multi-collateral loan permission in MCP.
5. If the user's intent is ambiguous (e.g. missing order_id, currency, or amount), ask a clarifying question before routing.

Domain Knowledge

Core Concepts

• Current loan: Flexible loan. Create via cex_mcl_create_multi_collateral with order JSON: order_type: current.
• Fixed loan: 7-day/30-day. order JSON must include order_type: fixed, fixed_type: 7d or 30d (lowercase), fixed_rate: hourly interest rate from cex_mcl_get_multi_collateral_fix_rate (use rate_7d or rate_30d for that borrow_currency; pass as-is, do not describe as annual or daily rate). Missing fixed fields may yield INVALID_PARAM_VALUE.
• Repay: cex_mcl_repay_multi_collateral_loan with repay_loan JSON.
• Add collateral: cex_mcl_operate_multi_collateral, collateral_adjust with type: append.
• Redeem collateral: same tool, type: redeem.
• LTV: cex_mcl_get_multi_collateral_ltv — init_ltv, alert_ltv, liquidate_ltv.

Create Loan Flow (Case 1 & 2)

1. Parse collateral, borrow currency/amount; fixed: 7 days → 7d, 30 days → 30d.
2. Current: Optionally cex_mcl_list_user_currency_quota or current rate tools. On confirm: cex_mcl_create_multi_collateral with order JSON.
3. Fixed: cex_mcl_get_multi_collateral_fix_rate; filter list by borrow_currency; on empty or no row, stop with user message; else set fixed_rate = rate_7d or rate_30d (hourly rate; pass as-is into order JSON; do not describe as annual or daily). On confirm: order JSON with fixed fields.

Repay Flow (Case 3)

1. Parse order_id and repay amount (or full).
2. Show draft; on confirm: cex_mcl_repay_multi_collateral_loan with repay_loan JSON.

Add / Redeem Collateral Flow (Case 4 & 5)

1. Parse order_id and collateral amount/currency.
2. Show draft; on confirm: cex_mcl_operate_multi_collateral with collateral_adjust JSON.

Presentation — order list / order detail (Case 6)

When the user asks to view my collateral loan orders or order detail:

• No time fields: Do not output any time or date information—omit every timestamp-style field from MCP (e.g. borrow_time, maturity, due time, operate_time, create_time, repay_time, calendar dates, Unix seconds as dates). Do not paraphrase relative timing (e.g. "expires in 3 days") computed from those fields.
• Allowed in reply: order_id, status, borrow side (currency, principal/interest left), collateral side (currency, amount), current LTV if present, fixed_type 7d/30d as term label only (no calendar dates).
• If the user asks specifically for dates/maturity: Reply that timing is not shown here and they should open Gate (app/web) for full order schedule—still do not paste API time fields into chat.

Safety Rules

• Writes (cex_mcl_create_multi_collateral, cex_mcl_repay_multi_collateral_loan, cex_mcl_operate_multi_collateral): Always require explicit confirmation and an order draft before execution.
• No investment advice: Present LTV/rates; user decides.
• Sensitive data: Never expose API keys or raw internal errors.
• Amounts: Reject non-positive amounts; validate order_id for repay/collateral ops.
• Order views: Never surface time columns, dates, or timestamp fields in order list/detail answers to the user.

Error Handling

Prompt Examples & Scenarios

See references/scenarios.md for prompt examples and expected behaviors (create current/fixed, repay, add collateral, redeem collateral).