Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official

pulse_trader_daily_stats

Retrieves a trader's daily PnL, trade count, win rate, and volume for each active day. Use for deep due diligence and consistency analysis.

Instructions

Get day-by-day performance breakdown for any trader. Returns daily PnL, trade count, win rate, and volume for each day the trader was active. Use for deep due diligence and identifying consistency patterns.

Input Schema

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

Implementation Reference

  • src/index.ts:726-738 (registration)
    Registration of the 'pulse_trader_daily_stats' MCP tool with its description, input schema (useToonFormat + Ethereum address), and handler that calls the API endpoint /pulse/trader/{address}/daily
    // TOOL 17: Trader Daily Stats
    // ══════════════════════════════════════════════════════════
    if (shouldRegister("pulse_trader_daily_stats")) server.registerTool(
      "pulse_trader_daily_stats",
      {
        description: "Get day-by-day performance breakdown for any trader. Returns daily PnL, trade count, win rate, and volume for each day the trader was active. Use for deep due diligence and identifying consistency patterns.",
        inputSchema: {
          useToonFormat: useToonFormatSchema,
          address: ethAddressSchema,
        },
      },
      async ({ useToonFormat, address }) => toolResult(await callAPI(useToonFormat, `/pulse/trader/${address}/daily`))
    );
  • Handler function for pulse_trader_daily_stats - takes useToonFormat and address parameters, calls the backend API at /pulse/trader/{address}/daily to fetch the trader's daily stats, and formats the result
      async ({ useToonFormat, address }) => toolResult(await callAPI(useToonFormat, `/pulse/trader/${address}/daily`))
    );
  • Input validation schema for pulse_trader_daily_stats: useToonFormat boolean (default true) and address validated as Ethereum address (0x followed by 40 hex chars)
    inputSchema: {
      useToonFormat: useToonFormatSchema,
      address: ethAddressSchema,
    },
  • The callAPI helper is used by the handler to make HTTP requests to the Coinversa API backend with timeout, retries, and error handling. The handler calls it with path `/pulse/trader/${address}/daily`.
    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");
    }
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses that the tool returns data for days the trader was active, which is helpful. However, it lacks details on data freshness, historical range, pagination, or whether it requires authentication. It does not contradict any annotations.

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 three sentences, front-loaded with the core action and output, followed by usage guidance. Every sentence adds value without redundancy.

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 simplicity (2 params, no output schema, no annotations), the description adequately covers purpose, output fields, and usage. It lacks details on error handling or empty results, but the listed fields are sufficient for basic understanding.

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 does not add semantic meaning beyond the schema; it summarizes the output but not the parameters. The schema already describes both parameters adequately.

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 the verb 'Get' and the resource 'day-by-day performance breakdown for any trader', listing specific fields (daily PnL, trade count, win rate, volume). It effectively distinguishes from sibling tools like pulse_trader_performance by focusing on daily granularity.

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 states 'Use for deep due diligence and identifying consistency patterns', providing clear context. While it does not mention alternatives or when not to use it, the purpose and sibling names imply the appropriate usage.

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