WOOFi Pro MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WOOFI_API_KEY | Yes | Your unique WOOFi Pro/Orderly API key | |
| WOOFI_ACCOUNT_ID | Yes | Your WOOFi Pro/Orderly account identifier | |
| WOOFI_SECRET_KEY | Yes | Your private WOOFi Pro/Orderly secret key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_account_infoA | Fetch account balances and fee tiers |
| get_positionsC | List open positions |
| create_orderC | Create a new regular order |
| batch_create_ordersB | Create multiple orders in batch |
| edit_orderC | Edit an existing order |
| cancel_orderB | Cancel an order by order ID |
| cancel_order_by_client_idB | Cancel an order by client order ID |
| cancel_all_pending_ordersC | Cancel all pending orders |
| cancel_all_afterC | Cancel all orders after a timeout |
| get_ordersC | Get orders with filtering options |
| get_order_by_idB | Get order by order ID |
| get_order_by_client_idC | Get order by client order ID |
| create_algo_orderC | Create an algorithmic order (stop loss, take profit, etc.) |
| edit_algo_orderD | Edit an existing algo order |
| cancel_algo_orderA | Cancel an algo order by order ID |
| cancel_algo_order_by_client_idB | Cancel an algo order by client order ID |
| cancel_all_pending_algo_ordersC | Cancel all pending algo orders |
| get_algo_ordersC | Get algo orders with filtering options |
| get_algo_order_by_idB | Get algo order by order ID |
| get_algo_order_by_client_idC | Get algo order by client order ID |
| get_asset_historyB | Get asset transaction history |
| get_holdingsC | Get asset holdings |
| create_withdraw_requestC | Create a withdrawal request |
| get_settle_pnl_nonceB | Get settle PnL nonce |
| request_pnl_settlementB | Request PnL settlement with EIP-712 signature |
| get_pnl_settlement_historyC | Get PnL settlement history |
| create_internal_transferC | Create internal transfer between accounts |
| get_internal_transfer_historyC | Get internal transfer history |
| get_all_positionsB | Get all positions |
| get_position_by_symbolB | Get position for specific symbol |
| get_position_historyC | Get position history |
| get_liquidated_positionsC | Get public liquidated positions |
| get_liquidationsC | Get user liquidation data |
| get_positions_under_liquidationC | Get positions under liquidation (public) |
| claim_liquidated_positionsB | Claim liquidated positions (POST with EIP-712 signature) |
| claim_insurance_fundC | Claim insurance fund (POST with EIP-712 signature) |
| get_insurance_fundB | Get insurance fund details |
| get_funding_fee_historyD | Get funding fee history |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 38 tools
Most tools target distinct actions and resources, but `get_liquidated_positions` and `get_positions_under_liquidation` are very similar, causing potential confusion. Overall, the tool purposes are clear.
All tools follow a consistent `verb_noun` pattern in snake_case, with minor variations like `batch_create_orders` and `create_withdraw_request` not breaking the overall predictability.
With 38 tools, the count exceeds the recommended range for coherence. While each tool has a specific purpose, the sheer number can overwhelm agents, and several duplicate-like patterns (e.g., multiple cancel and get order tools) inflate the count.
The tool set covers the core lifecycle of orders (create, read, cancel, edit), positions (list, detail, history), transfers, withdrawals, liquidations, and PnL settlement. Minor gaps like missing deposit or trade history exist but are acceptable for the server's focus.