Skip to main content
Glama

list_copy_trade_leaders

Top Hyperliquid accounts to copy, from Hyperliquid's public leaderboard. Only accounts over $25k that traded this month and are profitable all-time. Each row has profit per window, turnoverPerDay (volume / account value per day, last 30 days) and a trackRecord (30- and 90-day return, worst drop, Calmar) once FortFi has computed it. Accounts trading over 20x their account a day (market makers, high-frequency bots) are hidden unless includeHighTurnover=true. Use get_copy_trade_wallet and backtest_copy_trade before copying one.

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": "list_copy_trade_leaders"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo0-based page, default 0
sortNopnl (default): profit over window. return90d: best 90-day return. calmar90d: 90-day return / worst drop. worstDrop90d: smallest worst drop among profitable leaders. Track-record sorts skip leaders not yet computed
queryNoAddress prefix (0x...) or display name fragment
windowNoProfit window that must be positive and ranks sort=pnl. Default month
pageSizeNo1 to 50, default 20
maxTurnoverPerDayNoHide accounts trading more than this multiple of their account a day (default 20)
maxWorstDrop90dPctNoHide leaders whose 90-day worst drop is above this percent
includeHighTurnoverNoShow every account regardless of turnover

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / includeHighTurnover
      Added value: +{
      +  "description": "Show every account regardless of turnover",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / maxTurnoverPerDay
      Added value: +{
      +  "description": "Hide accounts trading more than this multiple of their account a day (default 20)",
      +  "type": "number"
      +}
    • addedInput schema / properties / maxWorstDrop90dPct
      Added value: +{
      +  "description": "Hide leaders whose 90-day worst drop is above this percent",
      +  "type": "number"
      +}
    • addedInput schema / properties / sort
      Added value: +{
      +  "description": "pnl (default): profit over window. return90d: best 90-day return. calmar90d: 90-day return / worst drop. worstDrop90d: smallest worst drop among profitable leaders. Track-record sorts skip leaders not yet computed",
      +  "enum": [
      +    "pnl",
      +    "return90d",
      +    "calmar90d",
      +    "worstDrop90d"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / window / description
      Previous value: -"Default month"New value: +"Profit window that must be positive and ranks sort=pnl. Default month"
    • changedInput schema / properties / window / enum
      Previous value: -[
      -  "week",
      -  "month",
      -  "allTime"
      -]New value: +[
      +  "day",
      +  "week",
      +  "month",
      +  "allTime"
      +]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden and discloses key eligibility rules: accounts must be over $25k, traded this month, and be profitable all-time. It also explains that high-turnover accounts are hidden by default unless includeHighTurnover=true, and notes that track records appear only once FortFi has computed them.

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 front-loaded with the tool's purpose, then covers eligibility, row contents, hidden-account behavior, and recommended next steps. Every sentence contributes useful information, and there is no redundant filler.

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?

For an eight-parameter listing tool with no annotations and no output schema, the description is largely complete: it explains eligibility, default filtering, row fields, and downstream validation steps. It still does not describe the overall response shape or any authentication/rate-limit behavior, which keeps it short of fully complete.

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 100%, so the input schema already documents all eight parameters thoroughly. The description reinforces the default 20x turnover filter and explains the meaning of high-turnover accounts, but it adds limited parameter meaning beyond what the schema already provides.

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 states a specific list resource: top Hyperliquid accounts to copy from the public leaderboard. It distinguishes this discovery tool from downstream inspection and backtesting tools by naming get_copy_trade_wallet and backtest_copy_trade.

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?

It gives clear usage context by saying to use get_copy_trade_wallet and backtest_copy_trade before copying one of these accounts. It does not explicitly state when not to use this list or name a direct alternative leaderboard-listing tool, but the workflow guidance is clear.

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