Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official

pulse_biggest_trades

Get the biggest winning or losing trades on Hyperliquid for market sentiment and narrative analysis.

Instructions

Get the biggest winning or losing trades across all of Hyperliquid. Use type='wins' for the largest profitable trades, or type='losses' for the largest losses. Useful for market sentiment and narrative analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
useToonFormatNoReturn data in compact toon format (default: true). Set to false for standard JSON.
typeYes'wins' for biggest profitable trades, 'losses' for biggest losing trades
limitNoNumber of trades to return
thresholdNoMinimum PnL for wins (e.g. 50000) or maximum PnL for losses (e.g. -50000)

Implementation Reference

  • src/index.ts:742-765 (registration)
    Registration of the 'pulse_biggest_trades' tool via server.registerTool(), with input schema, description, and the handler function.
    // ══════════════════════════════════════════════════════════
    if (shouldRegister("pulse_biggest_trades")) server.registerTool(
      "pulse_biggest_trades",
      {
        description: "Get the biggest winning or losing trades across all of Hyperliquid. Use type='wins' for the largest profitable trades, or type='losses' for the largest losses. Useful for market sentiment and narrative analysis.",
        inputSchema: {
          useToonFormat: useToonFormatSchema,
          type: z.enum(["wins", "losses"]).describe("'wins' for biggest profitable trades, 'losses' for biggest losing trades"),
          limit: z.number().min(1).max(50).default(20).describe("Number of trades to return"),
          threshold: z.number().optional().describe("Minimum PnL for wins (e.g. 50000) or maximum PnL for losses (e.g. -50000)"),
        },
      },
      async ({ useToonFormat, type, limit, threshold }) => {
        if (type === "wins") {
          const params: Record<string, string> = { limit: String(limit) };
          if (threshold !== undefined) params.minPnl = String(threshold);
          return toolResult(await callAPI(useToonFormat, "/pulse/biggest-wins", params));
        } else {
          const params: Record<string, string> = { limit: String(limit) };
          if (threshold !== undefined) params.maxPnl = String(threshold);
          return toolResult(await callAPI(useToonFormat, "/pulse/biggest-losses", params));
        }
      }
    );
  • Handler function for pulse_biggest_trades. Accepts type ('wins'|'losses'), limit, and optional threshold. Delegates to callAPI with '/pulse/biggest-wins' or '/pulse/biggest-losses' endpoints.
    async ({ useToonFormat, type, limit, threshold }) => {
      if (type === "wins") {
        const params: Record<string, string> = { limit: String(limit) };
        if (threshold !== undefined) params.minPnl = String(threshold);
        return toolResult(await callAPI(useToonFormat, "/pulse/biggest-wins", params));
      } else {
        const params: Record<string, string> = { limit: String(limit) };
        if (threshold !== undefined) params.maxPnl = String(threshold);
        return toolResult(await callAPI(useToonFormat, "/pulse/biggest-losses", params));
      }
    }
  • Input schema for pulse_biggest_trades: useToonFormat (boolean), type (enum 'wins'|'losses'), limit (1-50, default 20), threshold (optional number for min/max PnL filter).
    if (shouldRegister("pulse_biggest_trades")) server.registerTool(
      "pulse_biggest_trades",
      {
        description: "Get the biggest winning or losing trades across all of Hyperliquid. Use type='wins' for the largest profitable trades, or type='losses' for the largest losses. Useful for market sentiment and narrative analysis.",
        inputSchema: {
          useToonFormat: useToonFormatSchema,
          type: z.enum(["wins", "losses"]).describe("'wins' for biggest profitable trades, 'losses' for biggest losing trades"),
          limit: z.number().min(1).max(50).default(20).describe("Number of trades to return"),
          threshold: z.number().optional().describe("Minimum PnL for wins (e.g. 50000) or maximum PnL for losses (e.g. -50000)"),
        },
      },
  • build/index.js:533-555 (registration)
    Build version: registration and handler of pulse_biggest_trades. Same logic but in compiled JS.
    if (shouldRegister("pulse_biggest_trades"))
        server.registerTool("pulse_biggest_trades", {
            description: "Get the biggest winning or losing trades across all of Hyperliquid. Use type='wins' for the largest profitable trades, or type='losses' for the largest losses. Useful for market sentiment and narrative analysis.",
            inputSchema: {
                useToonFormat: useToonFormatSchema,
                type: z.enum(["wins", "losses"]).describe("'wins' for biggest profitable trades, 'losses' for biggest losing trades"),
                limit: z.number().min(1).max(50).default(20).describe("Number of trades to return"),
                threshold: z.number().optional().describe("Minimum PnL for wins (e.g. 50000) or maximum PnL for losses (e.g. -50000)"),
            },
        }, async ({ useToonFormat, type, limit, threshold }) => {
            if (type === "wins") {
                const params = { limit: String(limit) };
                if (threshold !== undefined)
                    params.minPnl = String(threshold);
                return toolResult(await callAPI(useToonFormat, "/pulse/biggest-wins", params));
            }
            else {
                const params = { limit: String(limit) };
                if (threshold !== undefined)
                    params.maxPnl = String(threshold);
                return toolResult(await callAPI(useToonFormat, "/pulse/biggest-losses", params));
            }
        });
Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It does not disclose whether the operation is read-only, any rate limits, or potential side effects. The description implies data retrieval but lacks transparency about scope or caching.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences and directly states purpose and basic usage. It is concise without unnecessary words, though it could be slightly more structured.

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?

With 4 parameters and no output schema, the description lacks details on limit, threshold, and useToonFormat. The type parameter is explained, but the threshold parameter's role in filtering PnL is omitted. The sibling context suggests many similar tools, but no guidance is given to distinguish.

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 baseline is 3. The description adds value by explaining the 'type' parameter in plain language ('wins' vs 'losses'), which repeats the schema but is clear. It does not cover other parameters like limit or threshold, but the schema descriptions suffice.

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?

The description clearly states the tool retrieves the biggest winning or losing trades across Hyperliquid, specifying the 'type' parameter for wins or losses. However, it does not differentiate from sibling tools like pulse_recent_trades or pulse_most_traded_coins, which lower the score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description only vaguely states it is 'useful for market sentiment and narrative analysis.' It provides no explicit guidance on when to use this tool versus alternatives, nor any conditions or exclusions.

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