Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official

pulse_token_leaderboard

Rank top traders for any cryptocurrency coin, displaying their profit/loss, trade count, win rate, and volume.

Instructions

Get the top traders for a specific coin. Answers questions like 'who are the best BTC traders?' or 'who profits most from SOL?'. Returns ranked traders with PnL, trade count, win rate, and volume for that specific coin.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
useToonFormatNoReturn data in compact toon format (default: true). Set to false for standard JSON.
coinYesCoin symbol (e.g. BTC, ETH, SOL). For builder dex markets use prefix:COIN (e.g. xyz:SILVER, km:OIL, cash:TSLA)
limitNoNumber of traders to return

Implementation Reference

  • src/index.ts:787-799 (registration)
    Tool registration: pulse_token_leaderboard is registered with server.registerTool(). It calls the API endpoint /pulse/token-leaderboard/{coin} with a limit parameter.
    if (shouldRegister("pulse_token_leaderboard")) server.registerTool(
      "pulse_token_leaderboard",
      {
        description: "Get the top traders for a specific coin. Answers questions like 'who are the best BTC traders?' or 'who profits most from SOL?'. Returns ranked traders with PnL, trade count, win rate, and volume for that specific coin.",
        inputSchema: {
          useToonFormat: useToonFormatSchema,
          coin: z.string().min(1).max(20).describe("Coin symbol (e.g. BTC, ETH, SOL). For builder dex markets use prefix:COIN (e.g. xyz:SILVER, km:OIL, cash:TSLA)"),
          limit: z.number().min(1).max(100).default(50).describe("Number of traders to return"),
        },
      },
      async ({ useToonFormat, coin, limit }) =>
        toolResult(await callAPI(useToonFormat, `/pulse/token-leaderboard/${normalizeCoin(coin)}`, { limit: String(limit) }))
    );
  • Input schema for pulse_token_leaderboard: accepts useToonFormat (boolean), coin (string 1-20 chars with builder dex prefix support), and limit (number 1-100, default 50).
      description: "Get the top traders for a specific coin. Answers questions like 'who are the best BTC traders?' or 'who profits most from SOL?'. Returns ranked traders with PnL, trade count, win rate, and volume for that specific coin.",
      inputSchema: {
        useToonFormat: useToonFormatSchema,
        coin: z.string().min(1).max(20).describe("Coin symbol (e.g. BTC, ETH, SOL). For builder dex markets use prefix:COIN (e.g. xyz:SILVER, km:OIL, cash:TSLA)"),
        limit: z.number().min(1).max(100).default(50).describe("Number of traders to return"),
      },
    },
  • Handler function: calls the API at /pulse/token-leaderboard/{coin} with the normalized coin symbol and limit parameter, then returns the result via toolResult().
      async ({ useToonFormat, coin, limit }) =>
        toolResult(await callAPI(useToonFormat, `/pulse/token-leaderboard/${normalizeCoin(coin)}`, { limit: String(limit) }))
    );
  • normalizeCoin helper function: uppercase the coin name while preserving a lowercase builder dex prefix (e.g. 'xyz:silver' → 'xyz:SILVER', 'btc' → 'BTC'). Used by pulse_token_leaderboard to normalize the coin input before calling the API.
    function normalizeCoin(raw: string): string {
      const idx = raw.indexOf(':');
      if (idx !== -1) {
        // Builder dex format — keep prefix lowercase, uppercase the coin
        return raw.slice(0, idx).toLowerCase() + ':' + raw.slice(idx + 1).toUpperCase();
      }
      return raw.toUpperCase();
    }
  • callAPI helper: makes HTTP requests to the Coinversa API with timeout, retries, and error handling. Used by pulse_token_leaderboard handler to make the actual API call.
    async function callAPI(useToon: boolean, path: string, params?: Record<string, string>): Promise<any> {
      const url = new URL(`${BASE}${path}`);
      if (params) {
        Object.entries(params).forEach(([key, value]) => {
          if (value !== undefined && value !== "") {
            url.searchParams.set(key, value);
          }
        });
      }
    
      let lastError: Error | null = null;
    
      for (let attempt = 0; attempt <= MAX_RETRIES; attempt++) {
        try {
          const controller = new AbortController();
          const timeout = setTimeout(() => controller.abort(), REQUEST_TIMEOUT_MS);
    
          const headers: Record<string, string> = {};
          if (API_KEY) headers["X-API-Key"] = API_KEY;
    
          const response = await fetch(url.toString(), {
            headers,
            signal: controller.signal,
          });
    
          clearTimeout(timeout);
    
          if (response.status === 429) {
            // Rate limited — retry after delay
            if (attempt < MAX_RETRIES) {
              await new Promise((r) => setTimeout(r, RETRY_DELAY_MS * (attempt + 1)));
              continue;
            }
            throw new Error("Rate limit exceeded. Please wait a moment and try again.");
          }
    
          if (response.status === 404) {
            throw new Error("Not found. The requested resource does not exist — check the address or symbol.");
          }
    
          if (response.status === 401) {
            throw new Error("Invalid API key. Check your COINVERSAA_API_KEY environment variable.");
          }
    
          if (!response.ok) {
            const body = await response.json().catch(() => null);
            const msg = body?.error || response.statusText;
            throw new Error(`Request failed (${response.status}): ${msg}`);
          }
    
          const data = await response.json();
          return useToon ? toonEncode(data) : data;
        } catch (err: any) {
          if (err.name === "AbortError") {
            lastError = new Error("Request timed out after 30 seconds. The server may be under heavy load — try again.");
          } else if (err.cause?.code === "ECONNREFUSED" || err.cause?.code === "ENOTFOUND") {
            lastError = new Error("Cannot connect to the Coinversa API. Check your COINVERSAA_API_URL setting and network connection.");
          } else {
            lastError = err;
          }
    
          // Retry on transient network errors
          if (attempt < MAX_RETRIES && (err.name === "AbortError" || err.cause?.code === "ECONNRESET")) {
            await new Promise((r) => setTimeout(r, RETRY_DELAY_MS * (attempt + 1)));
            continue;
          }
    
          throw lastError;
        }
      }
    
      throw lastError || new Error("Request failed after retries");
    }
Behavior2/5

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

No annotations are present, so the description carries full burden. It mentions the returned fields (PnL, trade count, win rate, volume) but does not disclose behavioral traits such as whether data is real-time, cached, requires authentication, or has rate limits. Minimal behavioral context beyond output format.

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: first states purpose, second gives examples and lists output fields. No redundant text. Front-loaded with the core action and resource, making it easy to parse.

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?

Despite no output schema, the description compensates by listing key return fields (PnL, trade count, win rate, volume). It specifies the coin parameter scope. However, it lacks details on whether data is current or historical, and does not mention default limit or pagination. Still, for a list endpoint with well-described parameters, it is mostly 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 coverage is 100% with each parameter described (coin, limit, useToonFormat). The description adds no additional meaning beyond the schema, e.g., simply reiterating 'for that specific coin' which is already in the coin param. Baseline 3 is appropriate as the schema does the heavy lifting.

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?

Description clearly states 'Get the top traders for a specific coin' with example questions like 'who are the best BTC traders?', providing a specific verb+resource. It distinguishes from sibling tools like pulse_leaderboard (general leaderboard) and pulse_trader_* (per-trader) by focusing on a single coin.

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 gives example questions but does not explicitly state when to use this tool versus alternatives like pulse_leaderboard or pulse_trader_token_stats. No when-not or exclusion criteria are provided, leaving the agent to infer usage context.

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