Skip to main content
Glama
polskidegen

polskidegen-hl-tracker

Official
by polskidegen

get_top_traders

Retrieve the top Hyperliquid traders ranked by PnL, ROI, or volume over a chosen time window, with filters to exclude market makers and low-volume accounts.

Instructions

Return the top N Hyperliquid traders by PnL / ROI / volume over a time window (24h, 7d, 30d, or all-time). Uses Hyperliquid's own public leaderboard endpoint — no API key, covers all 30k+ accounts. Returns addresses you can feed into get_positions / get_pnl_summary / get_fills for deeper analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
windowNoTime window: 24h (day), 7d (week), 30d (month), or all (all-time).24h
limitNoNumber of top traders to return (1–50, default 10).
sort_byNoRanking metric: pnl (total USD profit), roi (return on equity %), or volume (traded USD).pnl
min_account_valueNoOptional filter: minimum account value in USD (default 0, i.e. no filter). Use e.g. 100000 to exclude dust accounts.
min_volume_usdNoOptional filter: minimum traded volume in USD within the selected window (default 0, i.e. no minimum beyond the exclude_zero_volume default).
exclude_zero_volumeNoWhen true (default), skip accounts with zero traded volume in the selected window. These are typically vaults, settlement accounts, market-making pools, or inactive wallets holding unrealized PnL — not active traders. Set to false only when you explicitly want to see them.
exclude_market_makersNoWhen true (default), exclude market makers / HFT accounts. Detected via three heuristics: (1) turnover ratio (volume ÷ account value) above a per-window threshold — real directional traders rarely turn over >25× their equity in a week, MMs turn over 50–500×; (2) PnL efficiency (PnL ÷ volume) below 0.1% — MMs earn on spreads not direction; (3) display-name blacklist (auros, wintermute, jump, flow, gsr, amber, cumberland, b2c2, galaxy, dwf, hlp, vault, mm, etc.). Set to false to include MMs.
max_turnover_ratioNoAdvanced override for the turnover filter used by exclude_market_makers. If set, accounts where volume ÷ account_value exceeds this ratio are dropped. Defaults: 10 for 24h, 25 for 7d, 100 for 30d, no cap for all-time.
Behavior5/5

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

With no annotations, the description fully discloses behavior: public API, no auth, account coverage, and detailed filtering heuristics for exclude_market_makers. It leaves no ambiguity about what the tool does.

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 concise, front-loaded with purpose, and every sentence adds value. No redundancy or wasted words.

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

Completeness5/5

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

Despite no output schema, the description explains return values (addresses) and their use with other tools. It covers key aspects: purpose, data source, coverage, and integration, making it complete for agent understanding.

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%, so parameters are already well-documented. The description adds no extra parameter meaning beyond what the schema provides, meeting baseline expectations.

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 it returns top traders by PnL/ROI/volume over time windows, directly addressing what the tool does. It distinguishes from siblings by specifying the return of addresses for use with other analysis tools like get_positions.

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?

The description provides clear context: uses public endpoint, no API key, covers all 30k+ accounts, and advises feeding addresses into other tools. However, it lacks explicit when-not-to-use or alternatives among siblings.

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/polskidegen/polskidegen-hl-tracker'

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