Skip to main content
Glama

EmblemAI AgentWallet

nansen-perps: nansen_perp_leaderboard

nansen_perp_leaderboard
Read-onlyIdempotent

Leaderboard of the most profitable Hyperliquid traders across all coins over a window: total/realized/unrealized PnL, ROI, volume, trade count, account value. Use for 'best Hyperliquid traders to copy'. 5 credits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nansen_perp_leaderboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days ending now (default 30). Ignored when date_from is set.
pageNoPage number for pagination (default 1)
limitNoRows to return (1-100, default 20)
labelsNoRestrict to wallets with these Smart Money labels. 'Smart Trader' = historically profitable spot traders; 'Smart HL Perps Trader' = profitable Hyperliquid perp traders.
date_toNoExplicit end (YYYY-MM-DD or ISO 8601). Defaults to now.
min_roiNoMinimum ROI in percent
sort_byNoSort field (default total_pnl)
date_fromNoExplicit start (YYYY-MM-DD or ISO 8601). Overrides days.
sort_directionNoSort direction (default DESC)
min_total_pnl_usdNo
min_account_value_usdNoSkip tiny accounts

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, non-destructive open-world query, so the safety profile is covered. The description adds genuinely new behavioral information beyond that: the 5-credit cost and the exact set of metrics returned, both of which affect whether an agent should call it. It stops short of mentioning pagination behavior or row ordering defaults.

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?

Two tightly packed sentences with zero filler: purpose and metric scope first, the canonical use case and cost second. Every clause carries information the agent can act on.

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 11 optional parameters, no output schema, and rich annotations, the description covers what the tool returns, what it costs, and the ranking semantics. Minor gaps remain around pagination limits and how the two SMARTER money label enums change results, but nothing critical is missing for correct invocation.

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 91%, so the schema already documents nearly every parameter, including enums for sort_by and labels. The description only echoes the 'over a window' and 'across all coins' concepts, adding no filter syntax or default behavior beyond what the schema states; baseline 3 is appropriate.

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?

States a specific verb+resource: a leaderboard of the most profitable Hyperliquid traders, scoped to 'across all coins over a window', and enumerates the ranked metrics (PnL, ROI, volume, trades, account value). It does not, however, distinguish itself from the very similar sibling nansen_perp_pnl_leaderboard or nansen_pnl_leaderboard, so the agent must guess which leaderboard variant to pick.

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?

Gives one concrete use case ('best Hyperliquid traders to copy'), which implies when to reach for it. It offers no when-not conditions and names no alternative sibling, even though several near-identical leaderboard tools exist.

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