CallMcpTool(server="gate-wallet", toolName="chain.config", arguments={chain: "eth"})

❌ Gate Wallet MCP Server not configured

The MCP Server named "gate-wallet" was not found in Cursor. Please configure it as follows:

Method 1: Configure via Cursor Settings (recommended)
  1. Open Cursor → Settings → MCP
  2. Click "Add new MCP server"
  3. Fill in:
     - Name: gate-wallet
     - Type: HTTP
     - URL: https://your-mcp-server-domain/mcp
  4. Save and retry

Method 2: Edit configuration file manually
  Edit ~/.cursor/mcp.json and add:
  {
    "mcpServers": {
      "gate-wallet": {
        "url": "https://your-mcp-server-domain/mcp"
      }
    }
  }

If you do not have an MCP Server URL yet, please contact your administrator.

⚠️  Gate Wallet MCP Server connection failed

MCP Server configuration was found, but the remote service could not be reached. Please check:
1. Confirm the service URL is correct (is the configured URL accessible)
2. Check network connection (VPN / firewall may affect connectivity)
3. Confirm the remote service is running normally

🔑 Gate Wallet MCP Server authentication failed

MCP Server connected but API Key validation failed. This service has AK/SK authentication enabled (x-api-key header).
Please contact your administrator for a valid API Key and confirm the server configuration is correct.

CallMcpTool(
  server="gate-wallet",
  toolName="wallet.get_addresses",
  arguments={ account_id: "acc_12345", mcp_token: "<mcp_token>" }
)

{
  "addresses": {
    "eth": "0xABCdef1234567890ABCdef1234567890ABCdef12",
    "bsc": "0xABCdef1234567890ABCdef1234567890ABCdef12",
    "sol": "7xKXtg2CW87d97TXJSDpbD5jBkheTqA83TZRuJosgAsU"
  }
}

CallMcpTool(
  server="gate-wallet",
  toolName="wallet.sign_message",
  arguments={
    message: "Welcome to Uniswap! Sign this message to verify your wallet. Nonce: abc123",
    chain: "eth",
    account_id: "acc_12345",
    mcp_token: "<mcp_token>"
  }
)

CallMcpTool(
  server="gate-wallet",
  toolName="wallet.sign_message",
  arguments={
    message: "{\"types\":{\"EIP712Domain\":[{\"name\":\"name\",\"type\":\"string\"}],\"Permit\":[{\"name\":\"owner\",\"type\":\"address\"},{\"name\":\"spender\",\"type\":\"address\"},{\"name\":\"value\",\"type\":\"uint256\"}]},\"primaryType\":\"Permit\",\"domain\":{\"name\":\"USDC\"},\"message\":{\"owner\":\"0xABC...\",\"spender\":\"0xDEF...\",\"value\":\"1000000000\"}}",
    chain: "eth",
    account_id: "acc_12345",
    mcp_token: "<mcp_token>"
  }
)

{
  "signature": "0x1234abcd...ef5678"
}

CallMcpTool(
  server="gate-wallet",
  toolName="wallet.sign_transaction",
  arguments={
    raw_tx: "0x02f8...",
    chain: "eth",
    account_id: "acc_12345",
    mcp_token: "<mcp_token>"
  }
)

{
  "signed_tx": "0x02f8b2...signed..."
}

CallMcpTool(
  server="gate-wallet",
  toolName="tx.send_raw_transaction",
  arguments={
    signed_tx: "0x02f8b2...signed...",
    chain: "eth",
    mcp_token: "<mcp_token>"
  }
)

{
  "hash_id": "0xa1b2c3d4e5f6...7890"
}

Step 0: MCP Server connection check
  Call chain.config({chain: "eth"}) to probe availability
  ↓ Success

Step 1: Authentication check
  Confirm valid mcp_token and account_id
  No token → Guide to gate-dex-mcpauth for login
  ↓

Step 2: Get wallet address
  Call wallet.get_addresses({ account_id, mcp_token })
  Extract target chain address
  ↓

Step 3: Display address

  ────────────────────────────
  🔗 Wallet Connection Info

  Chain: {chain_name}
  Address: {address}

  Use this address for DApp connection.
  EVM chains (Ethereum/BSC/Polygon etc.) share the same address.
  ────────────────────────────

Step 0: MCP Server connection check
  ↓ Success

Step 1: Authentication check
  ↓

Step 2: Intent recognition + parameter collection
  Extract signing request from user input:
  - message: Content to sign (required)
  - chain: Target chain (optional, default eth)
  - Signing type: personal_sign or EIP-712 (auto-detect from message format)
  ↓

Step 3: Display signing content for confirmation

  ────────────────────────────
  ✍️ Message Signing Request

  Chain: {chain_name}
  Signing type: {personal_sign / EIP-712}
  Content to sign:
  {message_content}

  This signature does not create an on-chain transaction and does not consume Gas.
  Reply "confirm" to sign, "cancel" to abort.
  ────────────────────────────

  ↓ User confirms

Step 4: Execute signing
  Call wallet.sign_message({ message, chain, account_id, mcp_token })
  ↓

Step 5: Display signing result

  ────────────────────────────
  ✅ Signing complete

  Signature: {signature}

  Submit this signature to the DApp to complete verification.
  ────────────────────────────

Step 0: MCP Server connection check
  Call chain.config({chain: "eth"}) to probe availability
  ↓ Success

Step 1: Authentication check
  Confirm valid mcp_token and account_id
  No token → Guide to gate-dex-mcpauth for login
  ↓

Step 2: Intent recognition + parameter collection
  Extract DApp operation intent from user input:
  - Operation type (e.g. "add liquidity", "stake ETH", "mint NFT")
  - Target protocol/contract (e.g. Uniswap, Aave, Lido)
  - Amount and tokens
  - Chain (optional, can infer from context)

  For missing parameters, ask user one by one:

  ────────────────────────────
  Please provide DApp interaction info:
  - Operation: (required, e.g. "add ETH-USDC liquidity on Uniswap")
  - Chain: (optional, default Ethereum)
  - Amount: (may need multiple amounts depending on operation type)
  ────────────────────────────

  ↓ Parameters complete

Step 3: Get wallet info (cross-Skill: gate-dex-mcpwallet)
  Call wallet.get_addresses({ account_id, mcp_token }) → Get from_address
  Call wallet.get_token_list({ account_id, chain, mcp_token }) → Get balance
  ↓

Step 4: Security review (recommended step)
  Call token_get_risk_info({ chain, address: contract_address }) (cross-Skill: gate-dex-mcpmarket)
  Evaluate contract risk level
  ↓

Step 5: Agent builds transaction
  Based on DApp operation type, Agent encodes contract call calldata:
  a) Known protocol (Uniswap/Aave/Lido etc.): Encode per protocol ABI
  b) User provides ABI + parameters: Agent parses and encodes
  c) User provides complete calldata: Use directly

  Build transaction parameters:
  - to: Contract address
  - data: calldata
  - value: Amount of native token to send (if any)
  ↓

Step 6: Determine if Approve is needed
  If operation involves ERC20 token (non-native token):
  - Check if current allowance is sufficient
  - Insufficient → Execute Approve transaction first (see Flow D)
  ↓

Step 7: Agent balance validation (mandatory)
  Validation rules:
  a) Operation involves native token: native_balance >= amount + estimated_gas
  b) Operation involves ERC20 token: token_balance >= amount AND native_balance >= estimated_gas
  c) Gas only: native_balance >= estimated_gas

  Validation failed → Abort transaction:

  ────────────────────────────
  ❌ Insufficient balance, cannot execute DApp operation

  Required {symbol}: {required_amount}
  Current balance: {current_balance}
  Shortfall: {shortfall}

  Suggestions:
  - Reduce operation amount
  - Deposit tokens to wallet first
  ────────────────────────────

  ↓ Validation passed

Step 8: Display DApp transaction confirmation summary (mandatory gate)
  Display content see "DApp Transaction Confirmation Template" below.
  Must wait for user to explicitly reply "confirm" before proceeding.
  ↓

  User replies "confirm" → Proceed to Step 9
  User replies "cancel" → Abort transaction
  User requests modification → Return to Step 2

Step 9: Sign transaction
  Call wallet.sign_transaction({ raw_tx, chain, account_id, mcp_token })
  Get signed_tx
  ↓

Step 10: Broadcast transaction
  Call tx.send_raw_transaction({ signed_tx, chain, mcp_token })
  Get hash_id
  ↓

Step 11: Display result + follow-up suggestions

  ────────────────────────────
  ✅ DApp transaction broadcast successful!

  Operation: {operation_description}
  Transaction Hash: {hash_id}
  Block explorer: https://{explorer}/tx/{hash_id}

  Transaction submitted to network. Confirmation time depends on network congestion.

  You can:
  - View updated balance
  - View transaction details
  - Continue with other operations
  ────────────────────────────

Step 0: MCP Server connection check
  ↓ Success

Step 1: Authentication check
  ↓

Step 2: Determine Approve parameters
  - token_address: Token contract address to authorize
  - spender: Spender contract address (e.g. Uniswap Router)
  - amount: Authorization amount

  Agent recommends exact amount over unlimited:

  ────────────────────────────
  💡 Authorization amount recommendation

  This operation requires authorizing {spender_name} to use your {token_symbol}.

  Recommended options:
  1. Exact authorization: {exact_amount} {token_symbol} (only for this operation, more secure)
  2. Unlimited authorization: unlimited (no need to re-authorize for future operations, but higher risk)

  Please choose authorization method, or specify custom amount.
  ────────────────────────────

  ↓

Step 3: Build Approve calldata
  Encode ERC20 approve(spender, amount) function call:
  - function selector: 0x095ea7b3
  - spender: Contract address (32 bytes padded)
  - amount: Authorization amount (uint256)
  ↓

Step 4: Display Approve confirmation

  ────────────────────────────
  ========== Token Authorization Confirmation ==========
  Chain: {chain_name}
  Token: {token_symbol} ({token_address})
  Authorize to: {spender_name} ({spender_address})
  Authorization amount: {amount} {token_symbol}
  Estimated Gas: {estimated_gas} {gas_symbol}
  ===============================
  Reply "confirm" to execute authorization, "cancel" to abort.
  ────────────────────────────

  ↓ User confirms

Step 5: Sign + broadcast Approve transaction
  Call wallet.sign_transaction({ raw_tx: approve_tx, chain, account_id, mcp_token })
  Call tx.send_raw_transaction({ signed_tx, chain, mcp_token })
  ↓

Step 6: Approve success
  Display Approve transaction hash, continue with subsequent DApp operation (Flow C Step 9)

Step 0: MCP Server connection check
  ↓ Success

Step 1: Authentication check
  ↓

Step 2: Collect contract call info
  User provides:
  - Contract address
  - Function name or ABI
  - Function parameters
  - value (optional, needed when sending native token)
  - Chain
  ↓

Step 3: Agent encodes calldata
  Encode function call data based on ABI and parameters
  ↓

Step 4: Security review + balance validation + confirmation gate
  Same as Flow C Steps 4 ~ 8
  ↓

Step 5: Sign + broadcast
  Same as Flow C Steps 9 ~ 11

========== DApp Transaction Confirmation ==========
Chain: {chain_name}
DApp/Protocol: {protocol_name} (e.g. Uniswap V3)
Operation: {operation} (e.g. Add liquidity)
Contract address: {contract_address}
---------- Transaction Details ----------
{operation_specific_details}
(e.g. Token A: 0.5 ETH, Token B: 1000 USDC)
---------- Authorization Info ----------
{approve_info_if_needed}
(e.g. Approve required: USDC → Uniswap Router, amount: 1000 USDC)
(When no approval needed: No additional authorization required)
---------- Balance Info ----------
{token_symbol} balance: {balance} (sufficient ✅ / insufficient ❌)
{gas_symbol} balance (Gas): {gas_balance} (sufficient ✅)
---------- Fee Info ----------
Estimated Gas (Approve): {approve_gas} (if needed)
Estimated Gas (Transaction): {tx_gas} {gas_symbol}
---------- Security Check ----------
Contract security audit: {risk_level} (e.g. audited/low risk/high risk/unknown)
===============================
Reply "confirm" to execute, "cancel" to abort, or specify modifications.

Note: DApp interaction involves smart contract calls. Please confirm contract address and operation are correct.

========== ⚠️ DApp Transaction Confirmation (Security Warning) ==========
Chain: {chain_name}
Contract address: {contract_address}

⚠️ Security warning: This contract is unaudited or marked as high risk.
Interacting with unknown contracts may result in asset loss. Please confirm you trust this contract.

---------- Transaction Details ----------
{operation_details}
---------- Balance Info ----------
{balance_info}
---------- Fee Info ----------
{gas_info}
---------- Security Check ----------
Contract audit status: {risk_detail}
=================================================
Reply "confirm" to proceed anyway (at your own risk), "cancel" to abort.

gate-dex-mcpauth (login, get mcp_token + account_id)
  → gate-dex-mcpwallet (wallet.get_addresses → get address)
    → gate-dex-mcpwallet (wallet.get_token_list → validate balance)
      → gate-dex-mcpmarket (token_get_risk_info → contract security review)
        → gate-dex-mcpdapp (Approve? → confirm → sign → broadcast)
          → gate-dex-mcpwallet (view updated balance)

gate-dex-mcpauth (login)
  → gate-dex-mcpdapp (wallet.sign_message → return signature result)

❌ Invalid contract address format

Provided address: {user_input}
Expected format: {expected_format}

Please check the address is correct, complete, and matches the target chain.

Function signature: approve(address spender, uint256 amount)
Selector: 0x095ea7b3

Calldata structure:
0x095ea7b3
+ spender address (32 bytes, left-padded with zeros)
+ amount (32 bytes, uint256)

Example (approve Uniswap Router to use 1000 USDT, 6 decimals):
0x095ea7b3
000000000000000000000000 68b3465833fb72A70ecDF485E0e4C7bD8665Fc45  ← spender
00000000000000000000000000000000000000000000000000000000 3B9ACA00  ← 1000 * 10^6