MCP Tools Reference
The Sequence MCP server exposes 80 tools across fourteen categories (orders, market data, intelligence, portfolio, account, risk, algos, analytics, TCA, history, registry, research, system, funding). Each tool maps to a Sequence API endpoint and returns structured JSON data that AI assistants can reason about.
Orders
Tools for submitting, monitoring, and managing orders.
| Tool | Description | Example Use |
|---|---|---|
place_order | Submit a new order via the SOR | "Buy 0.5 BTC-USD at market" |
get_orders | List parent orders with optional filters by status and symbol | "Show my completed BTC orders" |
get_order | Get full details of a specific order including child orders, fills, and TCA | "What happened with order P-abc123?" |
cancel_order | Cancel an active order by parent ID | "Cancel my pending ETH order" |
amend_order | Modify an active order's quantity or price constraints | "Change my limit order to 0.3 BTC" |
get_fills | Get execution fills with venue, price, quantity, and fees | "Show fills for my last order" |
get_child_orders | View how the SOR split a parent order across venues | "How was my order routed?" |
get_execution_traces | Get microsecond-level lifecycle events from submission through fill | "Show the execution trace for order P-abc123" |
place_order, cancel_order, and amend_order are only available in the read-write toolset. The read-only server excludes these.
Market Data
Tools for accessing real-time prices, depth, and trading pair information.
| Tool | Description | Example Use |
|---|---|---|
get_market_data | Get best bid/offer across all venues, optionally filtered by symbol | "What's the BBO for ETH-USDT?" |
get_order_book | Get L2 depth with configurable levels (up to 100) | "Show the top 10 levels of BTC-USD" |
get_ohlc | Get OHLC candlestick data from a specific venue | "Get hourly candles for SOL-USD" |
get_nbbo | Get the consolidated National Best Bid and Offer across all venues | "What's the NBBO for all pairs?" |
get_arbitrage_opportunities | Detect cross-venue price discrepancies where bid > ask | "Are there any arb opportunities?" |
get_pairs | List all available trading pairs and which venues support each | "What pairs can I trade?" |
get_pair_venues | Get venues supporting a specific pair with symbol mappings | "Which exchanges have BTC-USDT?" |
get_ticker | Get DataEngine stats: mid price, 24h change, spread, depth, volatility | "What's the current ticker for ETH-USD?" |
get_data_ohlc | Get OHLC candles from Sequence's own NBBO stream (multi-venue) | "Show NBBO-derived 15m candles for BTC-USDC" |
get_trades | Get recent public trades across all venues for a symbol | "Show the last 50 BTC-USD trades" |
Positions
One tool for everything you hold — fiat cash, crypto, perps, and event contracts. Filter by venue or instrument kind.
| Tool | Description | Example Use |
|---|---|---|
get_positions | Unified positions with qty, entry/mark price, unrealized P&L, and portfolio totals. Supports venues and kinds filter args | "What are my open positions?" / "How much USD do I have on Kraken?" / "What's my NAV?" |
Filter args: venues (list, optional), kinds (list of fiat / crypto / perp / event_contract, optional), include_closed (bool, default false).
The older get_balances and get_portfolio_summary tools are deprecated — they hit REST endpoints that now return 404. Use get_positions with the appropriate kinds filter instead.
Account
Tools for account information and infrastructure status.
| Tool | Description | Example Use |
|---|---|---|
get_account | Get account tier, rate limits, monthly volume, and order count | "What's my account tier?" |
get_venues | Get connection status and last-seen time for all venue edges | "Are all exchanges connected?" |
get_fees | Get maker and taker fee tiers for each venue | "What are my Binance fees?" |
list_credentials | List which venues have API credentials configured (no secrets) | "Which exchanges have I connected?" |
Risk
Tools for emergency controls and risk management.
| Tool | Description | Example Use |
|---|---|---|
activate_kill_switch | Emergency stop -- cancels all orders and blocks new submissions | "Activate the kill switch" |
clear_kill_switch | Re-enable order submission after a kill switch event | "Clear the kill switch" |
cancel_all_venue_orders | Cancel all open orders on a specific venue | "Cancel everything on Binance" |
The kill switch is an emergency mechanism. Activating it cancels all active orders across all venues immediately. Only use it when you need to halt all trading activity.
Algos
Tools for managing WASM trading algorithms.
| Tool | Description | Example Use |
|---|---|---|
list_algos | List all deployed algorithms with status and symbol | "What algos are running?" |
deploy_algo | Upload and deploy a WASM binary to the execution engine | "Deploy my new market maker" |
start_algo | Start a deployed algorithm (begins receiving market data and trading) | "Start the BTC-USD algo" |
stop_algo | Stop a running algorithm (cancels its orders, stops callbacks) | "Stop the ETH-USDT algo" |
undeploy_algo | Remove a deployed algorithm entirely | "Undeploy the SOL algo" |
get_algo_logs | Get info, warning, and error log output from an algo | "Show logs for BTC-USD algo" |
get_algo_stats | Get runtime stats: trade count, position, latency, actions sent | "How is my market maker performing?" |
Algo management tools (deploy_algo, start_algo, stop_algo, undeploy_algo) are only available in the read-write toolset.
Analytics
Tools for market microstructure and execution quality analysis.
| Tool | Description | Example Use |
|---|---|---|
get_market_analytics | Deep analytics: NBBO, spread, L2 depth summary, bid/ask imbalance, per-venue breakdown | "Analyze BTC-USD market structure" |
get_execution_analytics | Aggregate execution quality: fill rate, slippage, savings vs benchmark, latency | "How good is my execution quality?" |
get_venue_quality | Per-venue metrics: fill rate, reject rate, ack latency, quality score | "Which venue has the best execution?" |
get_data_recon | CoinGecko reconciliation: drift in bps, price comparison, data quality status | "Is our market data accurate?" |
System
Tools for monitoring infrastructure and usage.
| Tool | Description | Example Use |
|---|---|---|
get_system_status | Health check: connected venues, system version, uptime | "Is the system healthy?" |
get_usage | MCP tool call count, monthly limit, remaining calls, tier info | "How many MCP calls have I used?" |
Tool Call Patterns
When using MCP tools through Claude, you can chain multiple queries naturally:
"What's the current BTC-USD spread across venues, and how does it compare to ETH-USD?"
The AI will call get_market_analytics for both symbols and synthesize the comparison.
"Show my last 5 completed orders and their TCA reports"
The AI will call get_orders with a status filter, then get_order for each to pull TCA details.
For complex analysis, the AI may make multiple tool calls in sequence. This is normal -- each call is fast and the results build on each other to form a complete picture.