Hyperliquid
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENTGLOB_RUNTIME_URL | Yes | Your backend's address. Required by the MCP server; if missing, it stops at once with a message saying which setting is missing. | |
| AGENTGLOB_RUNTIME_TOKEN | Yes | The token your backend expects. Required by the MCP server; if missing, it stops at once with a message saying which setting is missing. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hl_market_dataA | Read Hyperliquid market data: mid prices, the order book, candles, or perp metadata (asset list, size precision, max leverage). No account access, no signing. |
| hl_accountA | Read this agent's own Hyperliquid account: perp positions and margin, spot balances, open orders, recent fills, or portfolio history. The address is always this agent's own bound wallet — it cannot be pointed at another account. |
| hl_place_orderA | Place a limit order on Hyperliquid. Subject to owner-set limits: per-order and daily notional caps, a maximum leverage, and an asset allowlist. Exceeding a limit returns 403 with a cap_* code — do not retry or attempt to work around it. Hyperliquid has no market order: to cross the spread, send an aggressive limit price and accept the slippage explicitly. |
| hl_cancel_orderA | Cancel one resting order by its order id (oid), which comes from hl_account with kind=openOrders. |
| hl_set_leverageA | Set leverage for one asset. Bounded by the owner-set maximum; a higher value returns 403 leverage_exceeded. Raising leverage raises liquidation risk on any open position. |
| hl_transferA | Move USDC from the spot account into the perp account so it can back trades. This is the ONLY direction — perp-to-spot does not exist here, deliberately. Amount is whole US dollars (no cents: the dashboard sets the cents as a tracking tag and sends slightly less than requested). One transfer at a time per account; if one is unresolved, reconcile with hl_transfer_status before retrying. Bounded by the owner-set daily limit. |
| hl_transfer_statusA | Reconcile the account's in-flight transfer against the exchange ledger: reports landed, still-pending (with whether a retry is allowed yet), or blocked (an owner must clear a double-land). |
| hl_swapA | Convert a stablecoin held on the spot side — USDH, USDT0 or USDE — into USDC, so it can back perp trades. Only those three coins, only into USDC, and never below 0.99 USDC per coin: if no buyer pays that much, nothing sells. This is not spot trading and cannot buy any other coin. Minimum 11 (at the 0.99 floor that clears the exchange minimum of $10). It can fill partly — report soldSz and usdcReceived, not the amount asked for. Counts against the owner-set daily limit; only what actually sold is charged. |
| hl_account_statusA | Trading readiness for this agent's own account: whether Hyperliquid is enabled, the Trading Key is present, the exchange still honours its approval, and when that approval expires. Use this to explain WHY an order might be refused, instead of discovering it from the refusal. |
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 action (read market, read account, place, cancel, leverage, transfer, swap, status). The only mild overlaps are the paired read/write tools (hl_account vs hl_account_status, hl_transfer vs hl_transfer_status), but descriptions clearly differentiate them, so confusion is unlikely.
All tools use a consistent hl_ prefix and snake_case, mostly verb_noun (hl_place_order, hl_cancel_order, hl_set_leverage). A few are noun-only or noun_status (hl_account, hl_market_data, hl_swap, hl_account_status), a minor deviation from the pattern.
Nine tools is well-scoped for a trading server: reads, order management, leverage, funding movement, and readiness checks, with each tool earning its place. No redundant or filler tools.
Covers the core trading lifecycle: market data, account reads, place/cancel orders, leverage, transfers, swap, and status. Minor gaps like an amend/modify order, cancel-all, or direct order-status-by-id (only open-orders listing exists) are workable but slightly incomplete.