Skip to main content
Glama

Tape — Hyperliquid Analytics

Hyperliquid Market Pulse

tape_market_pulse
Read-onlyIdempotent

Key live Hyperliquid numbers in about 600 tokens: BTC and ETH marks, total 24h volume and open interest, the highest and most negative funding, a market-structure sentiment score, and the top wallets by 30-day PnL. 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": {},
    "name": "tape_market_pulse"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuinely useful non-annotation facts: the response fits in about 600 tokens (a context-budgeting signal) and the result carries provenance. It does not state refresh cadence, staleness, or latency, which keeps it off a 5.

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 payload list is dense, front-loaded, and every element is informative. However, the tail is boilerplate: 'Not trading advice. Not investment advice.' are near-duplicates, and the 'Independent. Not affiliated with...' sentences add little to tool selection. Roughly a third of the text does not help an agent decide or invoke.

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?

With no output schema, the description properly carries the burden of describing return contents, and it does so field by field at a stated token budget. The gap is that 'live' is not quantified — no cadence or staleness window — which matters for a market-data snapshot an agent may cache or re-call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters and the schema is an empty object, so there is nothing for the description to disambiguate. Baseline 4 applies; no misleading parameter claims are made.

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 enumerates exactly what the tool returns: BTC and ETH marks, 24h volume and open interest, funding extremes, a sentiment score, and top wallets by 30-day PnL. That is a specific, verifiable resource definition an agent can match against a request. It stops short of differentiating from siblings like tape_market_signals or tape_analytics, so it cannot reach a 5.

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?

There is no guidance on when to call this versus the many adjacent siblings (tape_market_signals, tape_markets_radar, tape_analytics), and no stated preconditions. The only usage-shaped text is the disclaimer block ('For educational purposes only...'), which constrains liability rather than selection. An agent is left to infer that this is the broad summary call.

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