Skip to main content
Glama

EmblemAI AgentWallet

nansen-perps: nansen_perp_pnl_leaderboard

nansen_perp_pnl_leaderboard
Read-onlyIdempotent

PnL leaderboard for ONE Hyperliquid coin: which traders made the most trading it (realized/unrealized PnL, ROI, current position, trade count). 5 credits.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "token_symbol": "<token_symbol>"
    },
    "name": "nansen_perp_pnl_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.
sort_byNoSort field (default pnl_usd_total)
date_fromNoExplicit start (YYYY-MM-DD or ISO 8601). Overrides days.
token_symbolYesHyperliquid coin symbol, e.g. 'BTC', 'ETH', 'SOL', 'HYPE'
sort_directionNoSort direction (default DESC)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The description adds one concrete behavioral fact, the 5-credit cost, which is useful for invocation budgeting, but says nothing about result size, ranking behavior ties, or empty-result handling.

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 sentences with zero filler, and the identifying scope (one Hyperliquid coin) and the returned metrics are front-loaded before the cost note. Nothing is repeated from the schema.

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 nine parameters, no output schema, and full annotation coverage, the description does the right jobs: it fixes the subject to a single coin and lists the payload fields an agent will receive. Only the cost note and metric list stand in for return-value documentation, which is adequate but thin for a leaderboard that supports sorting and pagination.

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% and every one of the nine parameters carries a clear description including defaults, ranges, and the days/date_from override rule. The description still adds value by pinning token_symbol to a single Hyperliquid coin and by naming the metric set that sort_by can address.

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 and resource ("PnL leaderboard for ONE Hyperliquid coin") and enumerates the metrics returned (realized/unrealized PnL, ROI, current position, trade count). The capitalized "ONE" carves out a clear scope that separates it from a general PnL leaderboard, though it never names a sibling explicitly.

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: use this when you want the top traders on a single Hyperliquid coin. There is no statement of when to prefer nansen_pnl_leaderboard, nansen_perp_leaderboard, or nansen_wallet_perp_pnl instead, so the agent must infer the boundary from the name alone.

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