Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official

pulse_trader_trades

Retrieve recent trades for a wallet address, showing buys, sells, sizes, prices, and PnL to support copy-trading and due diligence.

Instructions

Get recent trades for a specific wallet address. See exactly what a trader has been doing in the last minutes/hours — every buy, sell, size, price, and PnL. Essential for copy-trading and due diligence.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
useToonFormatNoReturn data in compact toon format (default: true). Set to false for standard JSON.
addressYesEthereum wallet address (0x...)
sinceNoTime window: e.g. '10m' (minutes), '1h' (hours), '1d' (days)1h
limitNoNumber of trades to return
coinNoFilter by coin symbol (e.g. BTC, ETH, SOL). For builder dex: prefix:COIN (e.g. xyz:SILVER)

Implementation Reference

  • src/index.ts:506-523 (registration)
    Registration of the pulse_trader_trades tool on the MCP server. Gated by shouldRegister() so it's only available when an API key is present (not in the free tier set).
    if (shouldRegister("pulse_trader_trades")) server.registerTool(
      "pulse_trader_trades",
      {
        description: "Get recent trades for a specific wallet address. See exactly what a trader has been doing in the last minutes/hours — every buy, sell, size, price, and PnL. Essential for copy-trading and due diligence.",
        inputSchema: {
          useToonFormat: useToonFormatSchema,
          address: ethAddressSchema,
          since: sinceSchema.default("1h"),
          limit: z.number().min(1).max(100).default(50).describe("Number of trades to return"),
          coin: z.string().optional().describe("Filter by coin symbol (e.g. BTC, ETH, SOL). For builder dex: prefix:COIN (e.g. xyz:SILVER)"),
        },
      },
      async ({ useToonFormat, address, since, limit, coin }) => {
        const params: Record<string, string> = { since, limit: String(limit) };
        if (coin) params.coin = normalizeCoin(coin);
        return toolResult(await callAPI(useToonFormat, `/pulse/trader/${address}/trades`, params));
      }
    );
  • Handler function for pulse_trader_trades. Takes address (wallet), since (time window), limit, and optional coin filter, builds query params, then calls the backend API at /pulse/trader/{address}/trades.
    async ({ useToonFormat, address, since, limit, coin }) => {
      const params: Record<string, string> = { since, limit: String(limit) };
      if (coin) params.coin = normalizeCoin(coin);
      return toolResult(await callAPI(useToonFormat, `/pulse/trader/${address}/trades`, params));
    }
  • Input schema for pulse_trader_trades: useToonFormat (boolean), address (Ethereum address regex), since (time window like '1h'), limit (1-100, default 50), and optional coin filter.
      inputSchema: {
        useToonFormat: useToonFormatSchema,
        address: ethAddressSchema,
        since: sinceSchema.default("1h"),
        limit: z.number().min(1).max(100).default(50).describe("Number of trades to return"),
        coin: z.string().optional().describe("Filter by coin symbol (e.g. BTC, ETH, SOL). For builder dex: prefix:COIN (e.g. xyz:SILVER)"),
      },
    },
  • The callAPI helper used by the tool handler to make HTTP requests to the Coinversa backend. Supports retries, timeouts, and error handling.
    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");
    }
  • NormalizeCoin helper used to format coin symbols (uppercasing coin name while preserving builder dex prefix case) for the API request parameters.
    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();
    }
Behavior3/5

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

No annotations exist, so the description carries full burden. It discloses the scope (recent trades per address) and data fields but lacks details on data freshness, rate limits, or side effects. The behavior is largely inferred.

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 with essential information front-loaded. Every sentence adds value: purpose, data content, and use case. No 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 absence of an output schema, the description partially compensates by listing returned fields. It covers the tool's purpose and data scope but omits details like sorting or aggregation. Schema covers parameter constraints.

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 parameters are described in the schema (100% coverage), so baseline is 3. The description adds no additional explanation for parameters beyond the schema; it only contextualizes output fields.

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 tool retrieves recent trades for a specific wallet address. It specifies the data content (buy, sell, size, price, PnL) and distinguishes it from sibling tools like pulse_trader_closed_positions by emphasizing recent activity.

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 clear usage context: 'Essential for copy-trading and due diligence.' It implies timeliness ('last minutes/hours') but does not explicitly exclude alternatives or state when not to use.

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