Skip to main content
Glama

Tape — Hyperliquid Analytics

Hyperliquid Analytics Bundle

tape_analytics
Read-onlyIdempotent

Unified read-only bundle: market consensus, pulse, live signals, funding extremes and the live alert queue, in one call. Prefer the narrower tools when you need one part. 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": {
      "feed": "alerts"
    },
    "name": "tape_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
feedNoSet to alerts to return only the live alert queue.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "feed": "alerts"
      +  }
      +]
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds only 'Result carries provenance', which is suggestive but unexplained, and the remaining text is legal boilerplate rather than behavioral detail. Nothing here contradicts the annotations.

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 and the sibling-routing advice are front-loaded and earn their place, but the trailing chain of disclaimers ('For educational purposes only. Not trading advice. Not investment advice. Independent. Not affiliated...') is four-plus sentences of boilerplate that does not help an agent select or invoke the tool.

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?

For an aggregate tool with no output schema, the description should convey what comes back; listing the five component feeds helps, but 'provenance' is never defined and there is no indication of result shape or size for a bundle spanning five data sources. Adequate but with a clear gap given the tool's breadth.

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 single 'feed' parameter is documented in-schema with its enum value and effect, so the schema does the work. The description never mentions the feed parameter, so it adds no meaning beyond the schema — baseline 3.

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 gives a specific verb-plus-resource framing ('Unified read-only bundle') and enumerates the component feeds it aggregates (market consensus, pulse, live signals, funding extremes, alert queue). That is enough for an agent to know it is a multi-feed aggregate rather than a single-purpose tool, though a couple of the named components ('funding extremes') do not map obviously onto any sibling name.

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

Usage Guidelines4/5

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

It explicitly routes the agent away from this tool for narrow needs: 'Prefer the narrower tools when you need one part.' That is a real use-this-vs-that rule. It stops short of saying when the bundle is preferable (e.g., one-shot overview vs. repeated single-feed polling), so it is not fully exhaustive.

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