Skip to main content
Glama

Tape — Hyperliquid Analytics

Hyperliquid Live Alerts

tape_live_alerts
Read-onlyIdempotent

The live alert queue: funding extremes, signal fires and consensus flips, each with a plain-English read. Filter by coins or severity, cap with limit. Result carries provenance. For educational purposes only. Not trading advice. Not investment advice. Independent. Not affiliated with Hyperliquid Labs or the Hyperliquid Foundation.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "coins": [
        "BTC"
      ],
      "limit": 10
    },
    "name": "tape_live_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinsNoRestrict to symbols, e.g. ["BTC"].
limitNoAlerts to return (all by default).
severityNoKeep only alerts at this severity label as returned by the feed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "coins": [
      +      "BTC"
      +    ],
      +    "limit": 10
      +  }
      +]
  2. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description still adds real context beyond them: it says the queue is live, that each alert carries a plain-English interpretation, and that results carry provenance, which tells the agent what evidence accompanies each row. It omits freshness/latency and whether the queue is paginated or bounded in time.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose clause is correctly front-loaded in sentence one, but roughly half the text is a repeated legal disclaimer (for educational purposes, not trading advice, not investment advice, independent, not affiliated) that carries no value for tool selection or invocation.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description bears the burden of explaining returns; it partially does so by naming the alert categories and the plain-English read and provenance. It does not describe an alert's fields (timestamp, coin, severity value, message) or whether older alerts are truncated, which leaves an agent guessing at the result shape.

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%, so coins, limit and severity are already documented and the baseline is 3. The description only restates the parameters ("filter by coins or severity, cap with limit") without adding meaning – notably it does not enumerate the severity labels, which the schema defers vaguely to "as returned by the feed".

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 first sentence names the resource (a live alert queue) and enumerates its contents – funding extremes, signal fires, consensus flips – each with a plain-English read, so an agent knows what it gets back. It stops short of distinguishing itself from the sibling tape_market_signals, which sounds like a plausible alternative source for the same signals.

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?

"Filter by coins or severity, cap with limit" describes how to call the tool, not when to choose it over tape_market_signals or tape_market_pulse. There is no statement of prerequisites, no when-not-to-use, and no named alternative; the remaining sentences are legal disclaimers rather than selection guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources