Skip to main content
Glama
Keel — Hyperliquid trading strategies

Keel — Hyperliquid trading strategies

by keel-trade

Read Account Execution Safety

keel_accounts_safety
Read-onlyIdempotent

Check an operator-gated Hyperliquid account’s execution safety state to see if it is halted, why, and how many frozen sessions or unresolved cancels block release.

Instructions

Read one Hyperliquid account's execution SAFETY state: whether the account is halted, which halt event is current, how many frozen sessions and unresolved cancels the release still waits on, the halt's authority tier, and the block reasons. A halted account executes nothing, so this is the answer to 'why has this deployment done nothing since ' when the bar-level view shows no attempts at all. OPERATOR-GATED: allowlisted platform and on-call operators only. Everyone else gets a refusal that no re-login can fix — report it as 'operator-only', never as an authentication problem. Do NOT use to release a halt: clearing one is an operator ceremony with a compare-and-set on the exact halt event, and it is deliberately not exposed on this surface. Do NOT use for local arming — keel arm live is a local file and is unrelated to this server-side halt.

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": {
      "account_id": "<account_id>"
    },
    "name": "keel_accounts_safety"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idYesAccount to inspect — from `keel_accounts_list` or a `keel_deployments_list` row.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.9.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations cover the read-only safety profile, but the description adds behavior they cannot: the tool is operator-gated, non-operators receive a refusal that re-login cannot fix and must be reported as 'operator-only', and halt release is deliberately not exposed. These are high-value operational facts beyond the schema/annotations.

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?

It is front-loaded with the core purpose, then layered with gating and two explicit exclusions. Despite its length, every sentence routes the agent (what it reads, who can call it, what it must not be used for), so 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 values need not be described, and the description still covers purpose, access constraints, refusal handling, and exclusions. For a single-parameter read tool, nothing an agent needs to invoke it correctly is missing.

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% and the single account_id parameter is already documented in the schema (including its source, keel_accounts_list / keel_deployments_list rows). The description adds no parameter-level detail beyond what the schema provides, so the 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?

The description states a specific verb+resource (read an account's execution safety state) and enumerates the concrete content: halt flag, current halt event, frozen sessions, unresolved cancels, authority tier, block reasons. It clearly differentiates itself from keel_account_status and keel_accounts_list by scoping to halt/execution-blocking state rather than general account status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit triggering condition ('why has this deployment done nothing since <time>'), names what it is not for (releasing a halt, local arming), and points to the distinguishing alternative ('keel arm live is a local file'). The agent knows both when to reach for it and when not to.

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