omx
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
OMX executes Hyperliquid orders inside limits the human set. Preview before submitting. Large or over-budget intents return an approval_id and wait for a human. You may trigger the kill switch; you cannot clear it or change limits, fees or keys.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_quoteB | Top of book, mid, data age and depth within the policy band for an agent-allowed coin. |
| preview_orderA | Dry run: planned child orders, policy decisions, fee bound, and whether a human must approve. side: buy|sell. algo: market|limit|twap|pov|chase. size in base units. Sends nothing. |
| submit_orderA | Submit an intent. Above the approval threshold or the daily agent budget it is queued for a human and an approval_id is returned instead; check it with approval_status. ALWAYS pass a fresh client_intent_id (8..40 chars, A-Z a-z 0-9 _ -) and REUSE it when you retry after a timeout or error: a repeated id returns the existing intent (status "duplicate", intent_id "ag-<client_intent_id>") and never sends a second order. |
| approval_statusB | State of a queued approval: pending, approved, rejected, expired, executed or failed. |
| order_statusC | Fill progress, average price, cost vs arrival mid, fees and block reasons of an intent. |
| cancel_orderC | Cancel an intent this agent (same client name) created, and its resting children. |
| kill_switchA | Stop all new orders and cancel resting ones. Agents can turn it on, never off. |
| account_summaryB | Equity, day P&L (flows excluded), positions, open orders and remaining agent budget. |
| policy_limitsA | Read-only view of the policy limits, agent thresholds and builder fee. |
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 9 tools
Each tool targets a distinct stage of the order lifecycle: pricing (get_quote), simulation (preview_order), execution (submit_order), approval state (approval_status), fill state (order_status), cancellation (cancel_order), and account/policy inspection. The boundary between preview_order and submit_order is explicitly clarified by the dry-run wording and 'Sends nothing' note. No two tools appear interchangeable.
Action tools follow a clean verb_noun snake_case pattern (get_quote, preview_order, submit_order, cancel_order), while read-only query tools use noun phrases (approval_status, order_status, account_summary, policy_limits). The split is readable and largely principled, though kill_switch and the noun-phrase group slightly break the single-pattern convention.
Nine tools is well-scoped for a trading execution agent, covering the full workflow without redundant operations. Each tool maps to a necessary step: quote, preview, submit, approval, status, cancel, kill switch, account, and policy.
The surface covers the core lifecycle including pre-trade simulation, approval handling, idempotent submission, cancellation, and emergency stop, with account and policy visibility. Minor gaps exist around amending orders and listing historical fills/open orders as dedicated operations, but these are workable via order_status and account_summary.