Skip to main content
Glama
Sign In
Hyperliquid

Hyperliquid

by cryptolir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

hl_place_order

Place a limit order on Hyperliquid within owner-set notional, leverage, and asset limits; cap breaches return 403 cap_* codes, so do not retry.

Instructions

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "coin": "<coin>",
      "isBuy": "<isBuy>",
      "px": "<px>",
      "sz": "<sz>"
    },
    "name": "hl_place_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
pxYesLimit price. Rounded server-side to the asset's tick rules.
szYesSize in units of the asset (not USD).
tifNoTime in force. Default Gtc.
coinYesAsset symbol, e.g. BTC. Must be in the agent's allowlist.
isBuyYestrue to buy/long, false to sell/short.
reduceOnlyNoOnly reduce an existing position. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does well: it discloses the owner-set constraint regime (per-order and daily notional caps, max leverage, allowlist) and the exact failure semantics (403 + cap_* code, no retry). It omits auth requirements and what a successful response contains, keeping it short of 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, all load-bearing: the core action, the constraint/failure behavior, and the market-order workaround. Front-loaded with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a write tool with no annotations and no output schema, it covers the critical traps (limits, error code, no-retry, no market orders). The main remaining gap is the success response shape and any auth prerequisite, which the agent would have to discover empirically.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all six parameters including the tif enum and reduceOnly are already documented inline. The description adds only the conceptual point that an aggressive px crosses the spread, which is marginal beyond the schema baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource ('Place a limit order on Hyperliquid') and implicitly distinguishes itself from siblings like hl_cancel_order and hl_swap. An agent immediately knows this is the order-entry tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives strong operational guidance: exceeding owner limits returns 403 with a cap_* code and must not be retried, and it explains how to emulate a market order since none exists. It does not explicitly route to sibling tools, but the when/when-not for this tool is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools