Skip to main content
Glama
Sign In

Ironflow: Hyperliquid data

by io.github.ironflowsh
OverviewDiscussionsAdmin

Stop a strategy on a paper box

stop_box_strategy
DestructiveIdempotent

Stop one strategy on a Hyperliquid paper box: its orders are cancelled and its position is closed at the book, unless close_position is false. The answer says stopping until the close fills, then list_box_strategies shows stopped. Needs only the box URL.

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": {
      "box": "<box>",
      "strategy_id": "<strategy_id>"
    },
    "name": "stop_box_strategy"
  }
}

Input Schema

NameRequiredDescriptionDefault
boxYesThe paper box: its base_url from create_ironbox, or the ibxs_ secret
strategy_idYesstrat_... from start_box_strategy or list_box_strategies
close_positionNofalse leaves its position open on the box; default true

Output Schema

NameRequiredDescriptionDefault
paperNotrue
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
strategyNoOne strategy on a paper box

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the bar is lower, yet the description still adds real value: what exactly gets destroyed (orders cancelled, position closed at market), the close_position=false escape hatch, and the asynchronous completion behavior ('stopping until the close fills'). It does not mention auth or error conditions, but the async detail is the non-obvious trait an agent needs.

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?

Three short sentences, front-loaded with the destructive effect and the key default. 'The answer says stopping until the close fills' is grammatically awkward but still conveys the async semantics; nothing is padding.

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

Completeness5/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 shape need not be explained. For a destructive, asynchronous, open-world stop operation the description covers the effect, the default, the opt-out, and the post-condition verification path via list_box_strategies — everything needed to invoke it safely.

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 the baseline is 3. The description restates close_position's effect but adds nothing about the required strategy_id, and 'Needs only the box URL' is mildly confusing given that strategy_id is also required.

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 verb and resource ('Stop one strategy on a Hyperliquid paper box') and immediately spells out the effect: orders cancelled, position closed at the book. It implicitly contrasts with start_box_strategy and list_box_strategies, but never names the sibling a confused agent should use instead.

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 only implied through the effect description and the closing 'Needs only the box URL' note, which suggests a low-friction call. There is no explicit when-to-use/when-not guidance and no named alternative (e.g. use start_box_strategy to resume), so the agent must infer the lifecycle.

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