Skip to main content
Glama

portal_hyperliquid_get_analytics

Retrieve Hyperliquid fill analytics including top traders, volume by coin, fees, and PnL. Use to get a big-picture snapshot of trading activity without stitching raw fills.

Instructions

Get the big-picture Hyperliquid fill analytics with top traders, volume by coin, fees, and PnL.

COMMON USER ASKS:

  • Hyperliquid fill snapshot

  • Who traded the most?

WHEN TO USE:

  • You want network-level Hyperliquid fill analytics.

  • You want to know who traded the most, which coins had volume, or how fees and PnL looked.

  • You want grouped aggregate sections without stitching raw fills together yourself.

DON'T USE:

  • You need individual fill records or OHLC candles.

EXAMPLES:

  • Hyperliquid fill snapshot: {"network":"hyperliquid-fills","timeframe":"1h"}

  • Who traded the most?: {"network":"hyperliquid-fills","timeframe":"1h"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinNoFilter by asset symbols (e.g., ["BTC", "ETH"])
modeNoExecution depth. Defaults to complete requested-window analysis; the optional fast value is only for explicitly bounded previews.deep
cursorNoContinuation cursor for ranked analytics sections
networkNoNetwork name (default: 'hyperliquid-fills')hyperliquid-fills
timeframeNoTime range: '1h', '6h', '24h'. Default: '1h'1h
to_timestampNoEnding timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now".
section_limitNoPer-section page size for ranked sections. Default: 6
from_timestampNoStarting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "6h ago".
response_formatNoResponse format: 'summary' (smallest snapshot), 'compact' (chat-sized ranked sections, default), 'full' (complete analytics).compact
Behavior2/5

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

No annotations are provided, so the description carries full burden. It describes the tool as aggregating data but does not explicitly state it is read-only, mention side effects, authorization needs, or rate limits. For a read-only analytics tool, this omission leaves behavioral uncertainty.

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?

The description is well-structured with distinct sections: main description, COMMON USER ASKS, WHEN TO USE, DON'T USE, EXAMPLES. It is concise (4 sentences plus examples) and front-loaded with the core purpose. Every sentence adds value.

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?

Given 9 optional parameters, no output schema, and no annotations, the description covers the main aspects: what the tool returns (aggregate sections), what it doesn't (individual fills, OHLC), and provides usage examples. It lacks behavioral details but otherwise is fairly complete for an analytics tool.

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% with parameter descriptions in the input schema. The tool description adds examples but does not provide significant additional meaning beyond the schema. Baseline 3 is appropriate as the schema already documents parameter semantics adequately.

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 clearly states 'Get the big-picture Hyperliquid fill analytics with top traders, volume by coin, fees, and PnL.' It uses a specific verb ('Get') and resource ('big-picture Hyperliquid fill analytics'), and distinguishes from siblings like portal_hyperliquid_query_fills (individual fills) and portal_hyperliquid_get_ohlc (OHLC). COMMON USER ASKS and EXAMPLES reinforce this.

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?

A dedicated 'WHEN TO USE' section lists use cases (network-level analytics, top traders, volume, fees, PnL, aggregated sections), and a 'DON'T USE' section explicitly excludes individual fills and OHLC candles. This provides clear when-to-use and when-not-to-use guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/subsquid-labs/portal-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server