Ironflow: Hyperliquid data

List Ironboxes

list_ironboxes

Read-only

The Ironboxes on this API key's account, the sandboxes where agents run and trade next to Hyperliquid: id, name, state (creating, running, stopped, deleted or error), size, mode, runtime and markets.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`data`	No	Ironboxes
`notice`	No	Present 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

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 8, 2026

addedOutput schema / properties / data / items / properties / activity_url

Added value: +{
+  "description": "Where to watch this box. Shown only with base_url"
+}

changedOutput schema / properties / data / items / properties / expires_at / description

Previous value: -"When a trial box ends and is removed, Unix milliseconds"New value: +"When a trial box ends at the latest, Unix milliseconds"

addedOutput schema / properties / data / items / properties / strategies_url

Added value: +{
+  "description": "Where to start strategies on this box. Shown only with base_url"
+}

Changed6 schema fields changedNov 8, 2026

addedOutput schema / properties / data / items / properties / base_url

Added value: +{
+  "description": "Set the Hyperliquid SDK's base_url to this. Shown only when a paper box is created or rotated"
+}

addedOutput schema / properties / data / items / properties / expires_at

Added value: +{
+  "description": "When a trial box ends and is removed, Unix milliseconds"
+}

addedOutput schema / properties / data / items / properties / paper

Added value: +{
+  "description": "True on a paper box: the agent's own simulated Hyperliquid account"
+}

addedOutput schema / properties / data / items / properties / snippet

Added value: +{
+  "description": "A first Python program for this box. Shown only when created or rotated"
+}

addedOutput schema / properties / data / items / properties / starting_balance_usd
```
Added value: +{
+  "description": "Starting balance of a new paper box"
+}
```

addedOutput schema / properties / data / items / properties / trial

Added value: +{
+  "description": "True on a keyless trial box"
+}

AddedNov 7, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), yet the description still adds real behavior: results are scoped to the calling API key's account, and the enumeration lists the state machine values (creating, running, stopped, deleted, error) that an agent would otherwise have to discover at runtime. It does not discuss pagination or freshness, but with those annotations the bar is lower.

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?

A single front-loaded sentence organized as resource, gloss, then a colon-delimited field list, with no filler clauses. Every element (account scoping, conceptual definition, returnable fields, state values) carries information the agent would not otherwise have.

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?

For a zero-parameter read with an output schema and read-only annotations, this is close to sufficient: it says what an Ironbox is, whose Ironboxes are returned, and what fields come back. The only real gap is the missing contrast with get_ironbox and any statement about result size or pagination.

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?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. The trailing field list ('id, name, state ... size, mode, runtime and markets') is a return-shape hint rather than parameter documentation, which is still useful framing for a no-argument call.

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 identifies the exact resource ('The Ironboxes on this API key's account') and even glosses it as 'the sandboxes where agents run and trade next to Hyperliquid', which is more than the title offers. It implies a collection read rather than a single fetch, but never uses a list verb and does not explicitly contrast itself with the singular get_ironbox sibling, so the agent infers the distinction from the plural name alone.

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?

There is no when-to-use or when-not-to-use statement, and no named alternative such as get_ironbox for a single sandbox. The phrase 'on this API key's account' does imply account-wide scope, but that is a scope constraint rather than routing guidance, so selection between list_ironboxes and the surrounding get_/create_/delete_ironbox tools is left to the agent.

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 tools Inspect

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.