Skip to main content
Glama
Sign In

Ironflow: Hyperliquid data

by io.github.ironflowsh
OverviewDiscussionsAdmin

Delete liquidation alert

delete_liquidation_alert
DestructiveIdempotent

Stop and remove one Hyperliquid liquidation alert from this API key's account; nothing more is sent to its destination.

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": {
      "id": "<id>"
    },
    "name": "delete_liquidation_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAlert id from list_liquidation_alerts

Output Schema

NameRequiredDescriptionDefault
idNoThe deleted alert's id
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
deletedNotrue

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint, idempotentHint and openWorldHint, but the description adds real context beyond them: deletion is confined to this API key's account, and alert delivery to the destination ceases ('nothing more is sent'). It does not say whether an unknown id errors or whether the action is recoverable.

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 with the action first and the scoping/delivery consequences second; no filler or redundant restatement of the title.

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 one-parameter destructive tool with annotations and an output schema, the definition covers action, scope and side effect adequately; only edge-case behavior (invalid id, irreversibility) is left unstated.

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% and the 'id' parameter is already documented as coming from list_liquidation_alerts, so the description adds no parameter meaning. Baseline 3 applies when the schema carries the load.

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 verb and resource ('Stop and remove one Hyperliquid liquidation alert') plus the scope ('from this API key's account'), which clearly separates it from the create/list/test liquidation-alert siblings.

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?

The usage is implied (delete an alert you want gone) and the account scoping is useful, but there is no explicit when-to-use/when-not guidance and no mention of the sibling tools an agent would use to locate or verify an alert.

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