Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official

pulse_leaderboard

Retrieve ranked trader leaderboard from Hyperliquid. Sort by PnL, win rate, volume, score, or risk-adjusted returns, and filter by time period and minimum trade count.

Instructions

Get ranked trader leaderboard. Sort by PnL, win rate, volume, score, or risk-adjusted returns. Filter by time period (day/week/month/allTime) and minimum trade count. Use this to find the best traders on Hyperliquid.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
useToonFormatNoReturn data in compact toon format (default: true). Set to false for standard JSON.
sortNoSort criteriapnl
periodNoTime periodallTime
limitNoNumber of traders to return
minTradesNoMinimum trade count filter

Implementation Reference

  • src/index.ts:345-362 (registration)
    Registration of the pulse_leaderboard tool with MCP server. It registers the tool name, description, input schema (sort, period, limit, minTrades), and handler that calls the /pulse/leaderboard API endpoint.
    // ══════════════════════════════════════════════════════════
    // TOOL 3: Leaderboard
    // ══════════════════════════════════════════════════════════
    if (shouldRegister("pulse_leaderboard")) server.registerTool(
      "pulse_leaderboard",
      {
        description: "Get ranked trader leaderboard. Sort by PnL, win rate, volume, score, or risk-adjusted returns. Filter by time period (day/week/month/allTime) and minimum trade count. Use this to find the best traders on Hyperliquid.",
        inputSchema: {
          useToonFormat: useToonFormatSchema,
          sort: z.enum(["pnl", "winrate", "volume", "score", "risk-adjusted", "losers"]).default("pnl").describe("Sort criteria"),
          period: z.enum(["day", "week", "month", "allTime"]).default("allTime").describe("Time period"),
          limit: z.number().min(1).max(100).default(20).describe("Number of traders to return"),
          minTrades: z.number().default(100).describe("Minimum trade count filter"),
        },
      },
      async ({ useToonFormat, sort, period, limit, minTrades }) =>
        toolResult(await callAPI(useToonFormat, "/pulse/leaderboard", { sort, period, limit: String(limit), minTrades: String(minTrades) }))
    );
  • Handler function: calls the remote API at /pulse/leaderboard with query parameters (sort, period, limit, minTrades) and returns the result formatted via toolResult(), optionally encoding in toon format.
      async ({ useToonFormat, sort, period, limit, minTrades }) =>
        toolResult(await callAPI(useToonFormat, "/pulse/leaderboard", { sort, period, limit: String(limit), minTrades: String(minTrades) }))
    );
  • Input schema for pulse_leaderboard: defines 5 parameters — useToonFormat (bool), sort (enum: pnl/winrate/volume/score/risk-adjusted/losers), period (enum: day/week/month/allTime), limit (1-100), minTrades (number).
      inputSchema: {
        useToonFormat: useToonFormatSchema,
        sort: z.enum(["pnl", "winrate", "volume", "score", "risk-adjusted", "losers"]).default("pnl").describe("Sort criteria"),
        period: z.enum(["day", "week", "month", "allTime"]).default("allTime").describe("Time period"),
        limit: z.number().min(1).max(100).default(20).describe("Number of traders to return"),
        minTrades: z.number().default(100).describe("Minimum trade count filter"),
      },
    },
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It states the tool returns a sorted and filtered leaderboard, but lacks details on data freshness, pagination, rate limits, or authentication. The output format (toon vs JSON) is only mentioned in parameter description, not the main description.

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 exceptionally concise: two sentences with no fluff. The first sentence states functionality and key options, the second provides usage context. Every word earns its place.

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

Completeness2/5

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

Given the tool has 5 parameters and no output schema, the description should explain what the returned leaderboard contains (e.g., trader names, stats). It does not describe the output structure, leaving agents uncertain about response format. The toon format detail is buried in the parameter description.

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?

All 5 parameters have descriptions in the schema (100% coverage), so the description adds limited value beyond repeating enum values (PnL, win rate, etc.) and the minTrades filter. The baseline score of 3 is appropriate since the schema already documents the parameters well.

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 retrieves a ranked trader leaderboard, specifying sort criteria and filters. It distinguishes itself from sibling tools like pulse_token_leaderboard (tokens) and pulse_trader_profile (individual trader details) by focusing on a ranked list of traders.

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 a clear usage context: 'Use this to find the best traders on Hyperliquid.' However, it does not explicitly contrast with alternatives like pulse_trader_profile or pulse_trader_trades for detailed data.

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/Coinversaa/mcp-server'

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