Skip to main content
Glama

Tape — Hyperliquid Analytics

Hyperliquid Sampled Leaderboard

tape_leaderboard
Read-onlyIdempotent

Sampled Hyperliquid wallets ranked by PnL, ROI, volume, and account value across time windows. This is not Hyperliquid's official leaderboard. Each row carries a labels object describing the wallet's activity mechanically: an activity band (turnover, or a no-volume / low-equity flag), a count of how many of the four published windows are positive, and an optional context flag that warns when the headline number is concentrated or short-history. Labels are mechanical descriptions of published figures computed by the rules at https://tapeperp.com/disclosures#labels, they are not ratings, endorsements, recommendations, or predictions of future results, and must not be restated as judgements about a trader's skill. Result carries provenance (feed endpoint and fetch time). In hosts that support MCP Apps this renders as a sortable table. 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": {
      "limit": 25,
      "metric": "pnl",
      "window": "day",
      "response_format": "CONCISE"
    },
    "name": "tape_leaderboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows to return (default 25).
metricNoRanking metric (default pnl).
windowNoLookback for the ranking metric (default day).
response_formatNoCONCISE (default): rank, address, raw numbers and labels. DETAILED adds the pre-formatted strings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "limit": 25,
      +    "metric": "pnl",
      +    "response_format": "CONCISE",
      +    "window": "day"
      +  }
      +]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the bar is lower. The description adds substantive context beyond them: the `labels` object structure (activity band, positive-window count, context flag for concentrated or short-history figures), `provenance` with feed endpoint and fetch time, and table rendering in MCP Apps hosts. It doesn't cover pagination or rate limits, but the data-interpretation caveats are genuinely useful.

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 is front-loaded, but the text is padded with repeated legal and educational disclaimers ('For educational purposes only. Not trading advice. Not investment advice. Independent. Not affiliated with...') that dilute the genuinely valuable mechanical-labels explanation.

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 a read-only tool with no output schema, it reasonably explains the returned row shape (labels, provenance) and rendering behavior. It omits ordering/tie-break rules, empty-result behavior, and how wallets are sampled, which matter for interpreting the response correctly.

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?

Schema description coverage is 100%, so baseline is 3. The description adds meaning beyond the schema by explaining that rows carry labels and that the four windows are the published windows, clarifying the scope of the `window` enum. It doesn't add syntax or defaults beyond what the schema already documents, so 4 rather than 5.

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 resource and operation: sampled Hyperliquid wallets ranked by PnL, ROI, volume, and account value across time windows, and explicitly distinguishes itself from the official Hyperliquid leaderboard. An agent can tell it apart from siblings such as tape_wallet_analysis or tape_analytics by the ranked-list output.

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?

Usage is implied – browse a sampled leaderboard – but the description never states when to prefer it over tape_wallet_analysis or tape_analytics, nor any exclusions or preconditions. Guidance is left to inference.

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