Skip to main content
Glama
Sign In

1gateway

by io.github.code0xff
OverviewDiscussionsAdmin

Hyperliquid liquidation price levels by leverage, vs the 24 h range, OI and funding crowding

hl_liquidations

Use when an agent sizes leverage on a Hyperliquid perp or checks how close typical positions are to liquidation. Input: coin, optional leverages (e.g. 5,10,20). Output: JSON mark, max leverage, maintenance margin, long/short liquidation price and distance % per leverage, whether the 24 h range exceeds it, 24 h high/low, OI USD, funding APR and crowded side. Estimates, not a live liquidation feed. Example: ?coin=BTC Price: $0.002 USDC (Base or Solana) via x402.

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>"
    },
    "name": "hl_liquidations"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinYesHyperliquid perp symbol (BTC, ETH, kPEPE) or HIP-3 dex:COIN (xyz:TSLA). Not listed or delisted: 400 before payment (not charged)
leveragesNoComma-separated leverages 1-100 (default 2,3,5,10,20,25,40,50 up to the coin's max)

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?

With no annotations, the description carries the full burden and does well: it discloses that outputs are estimates rather than a live liquidation feed, and surfaces the payment model ($0.002 USDC via x402 on Base or Solana). It does not cover rate limits or latency, but the key behavioral caveats are present.

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?

Front-loaded with the use case, then compact Input/Output breakdown, then caveat. The trailing example line is densely compressed and slightly awkward ('Example: ?coin=BTC Price: $0.002 USDC ... via x402'), but every element earns its place.

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?

No output schema exists, so the description must enumerate return fields, which it does thoroughly: mark, max leverage, maintenance margin, long/short liquidation prices and distance %, 24 h range comparison, high/low, OI USD, funding APR, and crowded side. Payment terms are also covered; only rate/limit behavior is absent.

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 the schema already documents coin formats, delisted-symbol handling, and the comma-separated leverage range. The description only echoes coin and an example leverage list, adding little semantic meaning beyond the schema.

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?

States a specific resource (Hyperliquid liquidation price levels by leverage) and a concrete decision it supports (sizing leverage, checking distance to liquidation). It is distinguishable from siblings like hl_perp_metrics or hl_funding_screener, though it partially overlaps them by also returning OI and funding.

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?

Opens with an explicit 'Use when' clause naming the two decision contexts (leverage sizing, liquidation proximity). It adds a caveat that results are estimates rather than a live feed, but names no alternative sibling tool or exclusion conditions.

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

All 1gateway toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources