Skip to main content
Glama
samklein952-hub

Hyperliquid MCP Server

get_open_orders

Retrieve all active orders for your connected wallet on the Hyperliquid exchange to monitor pending trades and manage positions.

Instructions

List all open orders for the connected wallet

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual handler implementation that fetches open orders from Hyperliquid. Validates wallet_address is set, calls info.open_orders() API, and formats the response with oid, symbol, side, price, size, and timestamp fields.
    def get_open_orders(self) -> list[dict[str, Any]]:
        """List all open orders."""
        if not self.wallet_address:
            raise ValueError("HYPERLIQUID_WALLET_ADDRESS is required.")
        orders = self.info.open_orders(self.wallet_address)
        return [
            {
                "oid": o.get("oid"),
                "symbol": o.get("coin"),
                "side": o.get("side"),
                "price": o.get("limitPx"),
                "size": o.get("sz"),
                "timestamp": o.get("timestamp"),
            }
            for o in orders
        ]
  • Tool registration in the MCP server. Defines the tool name, description, and empty input schema (no parameters required). This is where the tool is declared and made available to MCP clients.
    Tool(
        name="get_open_orders",
        description="List all open orders for the connected wallet",
        inputSchema={"type": "object", "properties": {}, "required": []},
    ),
  • Dispatch routing that maps the tool name to the actual handler call. When 'get_open_orders' is invoked, this case routes it to client.get_open_orders().
    case "get_open_orders":
        return client.get_open_orders()
  • Input/output schema definition for the tool. The inputSchema is empty (no arguments required), meaning this tool takes no parameters.
    Tool(
        name="get_open_orders",
        description="List all open orders for the connected wallet",
        inputSchema={"type": "object", "properties": {}, "required": []},
    ),
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses read-only behavior ('List') and authentication scope ('connected wallet'), but omits rate limits, pagination behavior, or what 'open' specifically means (unfilled vs pending cancellation).

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?

Single sentence, front-loaded with verb, zero waste. Appropriate length for the tool's simplicity.

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

Completeness3/5

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

Adequate for a zero-parameter read operation. Mentions 'connected wallet' establishing scope, but lacks return value description (relevant given no output schema exists). Missing clarification on what constitutes an 'open' order in this trading context.

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

Parameters4/5

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

Zero parameters present. Per rubric baseline for 0-param tools is 4. The description correctly implies no filtering parameters are accepted by stating 'all open orders'.

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

Purpose4/5

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

The description uses specific verb 'List' with clear resource 'open orders' and scope 'connected wallet'. It implicitly distinguishes from siblings like get_positions (filled trades) and get_orderbook (market depth) via standard trading terminology, though explicit differentiation is absent.

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

Usage Guidelines2/5

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

No explicit guidance on when to use versus alternatives (e.g., get_positions vs open orders) or prerequisites. The agent must infer usage solely from the tool name and trading context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/samklein952-hub/hyperliquid-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server