⚠️ STOP — You MUST read and strictly follow the shared runtime rules before proceeding.
Do NOT select or call any tool until all rules are read. These rules have the highest priority.
→ Read gate-runtime-rules.md
exist in the MCP server.
| MCP Server | Status |
|---|---|
| ------------ | -------- |
| Gate (main) | ✅ Required |
Query Operations (Read-only)
gate-mcp-cursor-installergate-mcp-codex-installergate-mcp-claude-installergate-mcp-openclaw-installerRead and strictly follow references/mcp.md, then execute this skill's VIP/fee query workflow.
SKILL.md keeps intent routing and rendering rules.references/mcp.md is the authoritative MCP execution layer for account/fee data retrieval and safe output behavior.Below are the most common prompts to get started quickly:
> What is my VIP level?
> Show me the spot and futures trading fees.
> Check my VIP level and trading fees.
| Group | Tool Calls |
|---|---|
| ------- | ------------ |
| Account / VIP tier | cex_account_get_account_detail |
| Trading fee rates | cex_wallet_get_wallet_fee |
cex_wallet_get_wallet_fee tool returns fee rates for both spot and futures in a single response. Use the settle parameter to query futures-specific fees.currency_pair parameter does not change the returned fee values — all trading pairs share the same account-level rate.settle parameter scope: The settle parameter only affects futures fee fields (futuresMakerFee / futuresTakerFee). Spot fees (makerFee / takerFee) remain unchanged regardless of settle.currency_pair handling: The API does not return an error for non-existent trading pairs. It silently returns the default account-level fees. Do not treat a successful response as confirmation that the trading pair exists.When the user asks about VIP tier or trading fees, follow this sequence.
Classify the request into one of these categories:
Key data to extract:
query_type: "vip", "fee", or "combined"currency_pair (optional): specific trading pair for fee lookupsettle (optional): futures settlement currency (BTC / USDT / USD)If query_type is "vip" or "combined":
Call cex_account_get_account_detail with:
Key data to extract:
vip_level: the user's current VIP tier (e.g., VIP 0, VIP 1, etc.)If query_type is "fee" or "combined":
Call cex_wallet_get_wallet_fee with:
currency_pair (optional): specify trading pair context (note: fee rates are account-level and do not vary by pair)settle (optional): futures settlement currency — affects futures fee fields onlyKey data to extract:
maker_fee_rate: spot maker fee ratetaker_fee_rate: spot taker fee ratefutures_maker_fee_rate: futures maker fee ratefutures_taker_fee_rate: futures taker fee rateFormat the response according to the Report Template. The API (cex_wallet_get_wallet_fee) always returns the full fee structure (spot + futures + delivery). Filter the output based on the user's original intent:
makerFee / takerFeefuturesMakerFee / futuresTakerFeecurrency_pair → append a note in the response: "Note: The API returns account-level fee rates. The fee shown applies to all trading pairs; if the pair you specified does not exist, the result still reflects your default account fee rate."Key data to extract:
| Condition | Action |
|---|---|
| ----------- | -------- |
| User asks about VIP tier/level only | Call cex_account_get_account_detail, return VIP level |
| User asks about trading fees only | Call cex_wallet_get_wallet_fee, return spot and futures fee rates |
| User asks about both VIP and fees | Call both tools, return combined result |
| User specifies a trading pair | Pass currency_pair parameter to cex_wallet_get_wallet_fee |
| User specifies futures settlement currency | Pass settle parameter to cex_wallet_get_wallet_fee |
| User asks about spot fees only | Call cex_wallet_get_wallet_fee, return only spot fee portion |
| User asks about futures/contract fees only | Call cex_wallet_get_wallet_fee with settle parameter, return only futures fee portion |
User specifies a currency_pair | Append a disclaimer that the API does not validate trading pairs; the returned fee is the account-level default and the pair may not exist |
| API returns error or empty data | Inform user of the issue and suggest checking account authentication |
## Query Result
{vip_section}
{fee_section}
VIP Section (when VIP is queried):
### VIP Tier
| Item | Value |
|------|-------|
| VIP Level | {vip_level} |
Fee Section (when fees are queried):
### Trading Fee Rates
| Category | Maker Fee | Taker Fee |
|----------|-----------|-----------|
| Spot | {spot_maker_fee} | {spot_taker_fee} |
| Futures | {futures_maker_fee} | {futures_taker_fee} |
Combined example output:
## Query Result
### VIP Tier
| Item | Value |
|------|-------|
| VIP Level | VIP 1 |
### Trading Fee Rates
| Category | Maker Fee | Taker Fee |
|----------|-----------|-----------|
| Spot | 0.1% | 0.1% |
| Futures (USDT) | 0.015% | 0.05% |
| Error Type | Typical Cause | Handling Strategy |
|---|---|---|
| ------------ | --------------- | ------------------- |
| Authentication failure | API key invalid or expired | Inform user to check MCP configuration and API key validity |
| Empty response | Account data not available | Inform user the query returned no data and suggest retrying |
| Network error | MCP connection issue | Suggest user check MCP server connectivity |
共 2 个版本