hypersignal

Get open orders

hl_get_open_orders

Read-onlyIdempotent

Retrieve open resting orders for any EVM address on Hyperliquid. View order details including coin, side, price, size, and trigger info.

Instructions

Open resting orders for an address: coin, side, price, size, order id, type, and trigger info. Read-only; paginated. Use to inspect any wallet's live order book footprint.

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": {
      "address": "<address>"
    },
    "name": "hl_get_open_orders"
  }
}

Input Schema

Name	Required	Description
`coin`	No	Optional filter to a single coin.
`limit`	No
`offset`	No
`address`	Yes	EVM 0x address.

Output Schema

Name	Required	Description	Default
`total`	Yes
`orders`	Yes
`address`	Yes
`nextOffset`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jul 25, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already indicate readOnly, idempotent, and non-destructive behavior. The description adds that it is paginated and lists the returned fields, providing useful additional context beyond annotations.

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?

Two concise sentences that front-load the core purpose and key details. No redundant or unnecessary information.

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?

Given the presence of an output schema and relatively simple parameters, the description covers the essential aspects: what it returns and that it is paginated. Could mention limit/offset defaults but not critical.

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 coverage is 50% with address and coin having descriptions. The description does not elaborate on parameters beyond stating pagination, but parameter names are self-explanatory. No significant added value over schema.

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?

Clearly states it retrieves open resting orders for a given address, listing the fields returned. Distinguishes itself from sibling tools by focusing on live order book footprint and being read-only.

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?

Explicitly says 'Use to inspect any wallet's live order book footprint', providing clear usage context. Does not explicitly exclude other use cases but implies the tool's purpose well.

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

Deploy Server