Skip to main content
Glama

Hl orderbook edge

hl_orderbook_edge
Read-onlyIdempotent

Hyperliquid L2 orderbook depth & execution simulator: returns best bid/ask, spread bps, top-5/top-20 orderbook imbalance (OBI), exact buy/sell VWAP slippage per USD size, and resting liquidity walls. $0.002 per call over x402 or X-API-Key. Not advice.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hl_orderbook_edge"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinNoHyperliquid perp coin ticker (default BTC, e.g. ETH, SOL, HYPE).
sizesNoComma-separated USD order sizes (default 1000,10000,50000,100000).
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive safety profile, so the description adds real value on the axes annotations cannot express: pay-per-call pricing ($0.002), the two accepted auth paths (x402 PAYMENT-SIGNATURE or X-API-Key), and a 'not advice' disclaimer. It stops short of describing response shape or rate/latency behavior, which is the main remaining gap.

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

Conciseness4/5

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

It is a single dense sentence, front-loaded with the identity of the tool before the output enumeration, with zero filler — the pricing and disclaimer clauses each earn their place. Slightly run-on, since five separate output metrics are chained together, but nothing is redundant.

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?

With no output schema, the description must carry return-value information, and it does so by naming each returned metric. Auth and pricing are covered, and the portmanteau defaults make it callable with zero required parameters. Only the precise response structure (units, nesting, ordering of the sizes array) remains underspecified.

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 each parameter (coin ticker, comma-separated USD sizes, x402 payment payload) is already documented in the schema. The description reinforces that sizes are USD-denominated and that slippage is quoted per USD size, but adds no syntax or format detail beyond the schema. Baseline 3 applies.

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?

The description names a specific resource (Hyperliquid L2 orderbook depth) and a specific capability (execution simulation), then enumerates the concrete outputs: best bid/ask, spread bps, top-5/top-20 OBI, VWAP slippage per USD size, and liquidity walls. Naming 'Hyperliquid' distinguishes it from the kalshi_orderbook and polymarket_orderbook siblings without opening either schema.

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

Usage Guidelines3/5

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

Usage is implied by the enumerated outputs — an agent can infer that this is the tool for pre-trade slippage checks on Hyperliquid perps — but there is no explicit when-to-use, when-not-to-use, or routing statement toward siblings. The parameter defaults (BTC, 1000/10000/50000/100000) give practical context but not selection guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources