Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official

pulse_global_stats

Retrieve global Hyperliquid trading statistics including total traders, trades, volume, PnL, and coverage period to assess overall market scale.

Instructions

Get global Hyperliquid trading statistics: total traders, trades, volume, PnL, and data coverage period. Use this to understand the overall scale of the market.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
useToonFormatNoReturn data in compact toon format (default: true). Set to false for standard JSON.

Implementation Reference

  • src/index.ts:238-245 (registration)
    Registration of the pulse_global_stats tool with the MCP server, including its description, input schema (optional useToonFormat boolean), and the handler that delegates to the callAPI helper.
    if (shouldRegister("pulse_global_stats")) server.registerTool(
      "pulse_global_stats",
      {
        description: "Get global Hyperliquid trading statistics: total traders, trades, volume, PnL, and data coverage period. Use this to understand the overall scale of the market.",
        inputSchema: { useToonFormat: useToonFormatSchema },
      },
      async ({ useToonFormat }) => toolResult(await callAPI(useToonFormat, "/pulse/stats"))
    );
  • Handler function: takes useToonFormat, calls the Coinversa API at /pulse/stats endpoint, and wraps the result via toolResult() for MCP response format.
    async ({ useToonFormat }) => toolResult(await callAPI(useToonFormat, "/pulse/stats"))
  • Shared input schema (useToonFormatSchema) used by pulse_global_stats and other tools. Accepts a boolean defaulting to true.
    const useToonFormatSchema = z
      .boolean()
      .default(true)
      .describe("Return data in compact toon format (default: true). Set to false for standard JSON.");
  • Helper function that wraps API response data into the MCP text content format for tool results.
    function toolResult(data: any) {
      return { content: [{ type: "text" as const, text: formatJSON(data) }] };
    }
  • Generic API helper that pulse_global_stats uses to call the /pulse/stats endpoint on the Coinversa backend with timeout, retries, and optional toon-format encoding.
    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 provided, so the description carries full responsibility for behavioral disclosure. It neither mentions read-only nature, caching, rate limits, nor any side effects. The description only states what it returns, not how it behaves.

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 concise sentences: one listing retrieved metrics, one stating usage purpose. Every word adds value. No redundant or verbose phrasing.

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?

Given the simple tool (one optional param, no output schema), the description adequately lists the returned fields and usage. It could be improved by mentioning the return format (JSON/object) but currently covers the essential information.

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?

The single parameter 'useToonFormat' is fully described in the input schema (default, meaning, format control). The description adds no additional context beyond the schema. With 100% schema coverage, a baseline of 3 is appropriate.

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 global Hyperliquid trading statistics including specific metrics like total traders, trades, volume, PnL, and data coverage period. This distinctly differentiates it from sibling tools that focus on specific subsets (e.g., pulse_biggest_trades, pulse_leaderboard).

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 explicitly advises to 'use this to understand the overall scale of the market,' providing clear context for when to employ this tool. However, it does not specify when not to use it or mention alternative tools for more granular 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