Skip to main content
Glama
Sign In

Ironflow: Hyperliquid data

by io.github.ironflowsh
OverviewDiscussionsAdmin

Auto-deleveraging fills

get_auto_deleveraging
Read-only

Hyperliquid auto-deleveraging (ADL) fills, newest first, across all markets or one: profitable positions Hyperliquid closed to cover a liquidation its backstop could not absorb. Per fill: wallet, market, side, price, size, notional, realized PnL, trade id (shared with the liquidated side) and transaction hash. Recorded from 2026-08-01; the default window is the last 7 days. For the liquidated side use get_liquidations.

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": "get_auto_deleveraging"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days back (default 7)
limitNoNumber of fills (1-1000, default 100)
marketNoOptional market filter: BTC-PERP or a Hyperliquid name (BTC, xyz:NVDA)

Output Schema

NameRequiredDescriptionDefault
dataNoADL fills
countNoFills returned
noticeNoPresent when the API added a note: how a market name was read, that data starts later than asked because of the history window, or a next step such as a free key
recorded_fromNoFirst moment recorded, Unix milliseconds

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely useful behavior beyond that: newest-first ordering, a data availability boundary (recorded from 2026-08-01), the 7-day default window, and the fact that the trade id is shared with the liquidated side — a non-obvious join key. The per-fill field enumeration partially duplicates the output schema, which keeps it from a 5.

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 resource and scope, then the definition, then the routing hint — the important facts come first. The dense per-fill field list is the one stretch that could be trimmed since the output schema already enumerates those fields.

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?

An output schema exists, so return values needn't be explained, and the description still covers data origin, ordering, default window, and the sibling alternative. The only residual gap is whether the limit applies per-market or globally, which an agent must infer.

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 100%, so all three parameters are already documented, including the days default and the 1-1000 limit range. The description only restates the 7-day default and the 'all markets or one' framing of the market filter, adding no syntax or edge-case 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?

States a specific resource (Hyperliquid auto-deleveraging fills) with scope (all markets or one), ordering (newest first), and defines the phenomenon itself — positions closed to cover a liquidation the backstop could not absorb. It explicitly routes the liquidated side to get_liquidations, so an agent can separate it from that sibling without opening a schema.

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 a clear alternative with its selection condition: 'For the liquidated side use get_liquidations.' It also states the default window and the data start date, which sets expectations. It stops short of contrasting with get_fills, the other plausible confusion point, but the usage context is otherwise unambiguous.

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

All Ironflow: Hyperliquid data 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