Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official

pulse_recent_closed_positions

Retrieve recently closed positions across all traders with entry/exit prices and hold duration. Filter by coin, minimum size, and hold time to find HFT trades, stopped-out positions, or large closings.

Instructions

Get recently closed positions across all traders. See what positions were just closed in the last N minutes/hours — with entry/exit prices and hold duration. Filterable by coin, minimum notional size, and hold duration range. Use to find: sub-second HFT trades (maxDuration=1000), positions that just got stopped out, large positions that just closed (minNotional=100000), quick scalps vs long holds.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
useToonFormatNoReturn data in compact toon format (default: true). Set to false for standard JSON.
sinceNoTime window: e.g. '10m' (minutes), '1h' (hours), '1d' (days)1h
limitNoNumber of positions to return
coinNoFilter by coin symbol (e.g. BTC, ETH, SOL). For builder dex: prefix:COIN (e.g. xyz:SILVER)
minNotionalNoMinimum notional value in USD (e.g. 100000 for $100K+ positions)
minDurationNoMinimum hold duration in milliseconds (e.g. 60000 for positions held at least 1 minute)
maxDurationNoMaximum hold duration in milliseconds (e.g. 1000 for sub-second HFT trades, 60000 for under 1 minute)

Implementation Reference

  • src/index.ts:890-914 (registration)
    Tool registration for 'pulse_recent_closed_positions'. Defines the tool name, description, input schemas (zod), and the async handler that calls the API endpoint '/pulse/closed-positions/recent' with filtered query parameters.
    // TOOL 26: Recent Closed Positions (Global)
    // ══════════════════════════════════════════════════════════
    if (shouldRegister("pulse_recent_closed_positions")) server.registerTool(
      "pulse_recent_closed_positions",
      {
        description: "Get recently closed positions across all traders. See what positions were just closed in the last N minutes/hours — with entry/exit prices and hold duration. Filterable by coin, minimum notional size, and hold duration range. Use to find: sub-second HFT trades (maxDuration=1000), positions that just got stopped out, large positions that just closed (minNotional=100000), quick scalps vs long holds.",
        inputSchema: {
          useToonFormat: useToonFormatSchema,
          since: sinceSchema.default("1h"),
          limit: z.number().min(1).max(200).default(50).describe("Number of positions 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)"),
          minNotional: z.number().optional().describe("Minimum notional value in USD (e.g. 100000 for $100K+ positions)"),
          minDuration: z.number().optional().describe("Minimum hold duration in milliseconds (e.g. 60000 for positions held at least 1 minute)"),
          maxDuration: z.number().optional().describe("Maximum hold duration in milliseconds (e.g. 1000 for sub-second HFT trades, 60000 for under 1 minute)"),
        },
      },
      async ({ useToonFormat, since, limit, coin, minNotional, minDuration, maxDuration }) => {
        const params: Record<string, string> = { since, limit: String(limit) };
        if (coin) params.coin = normalizeCoin(coin);
        if (minNotional != null) params.minNotional = String(minNotional);
        if (minDuration != null) params.minDuration = String(minDuration);
        if (maxDuration != null) params.maxDuration = String(maxDuration);
        return toolResult(await callAPI(useToonFormat, "/pulse/closed-positions/recent", params));
      }
    );
  • Handler function for pulse_recent_closed_positions. Extracts params (since, limit, coin, minNotional, minDuration, maxDuration), normalizes coin if provided, and calls the backend API at /pulse/closed-positions/recent.
    async ({ useToonFormat, since, limit, coin, minNotional, minDuration, maxDuration }) => {
      const params: Record<string, string> = { since, limit: String(limit) };
      if (coin) params.coin = normalizeCoin(coin);
      if (minNotional != null) params.minNotional = String(minNotional);
      if (minDuration != null) params.minDuration = String(minDuration);
      if (maxDuration != null) params.maxDuration = String(maxDuration);
      return toolResult(await callAPI(useToonFormat, "/pulse/closed-positions/recent", params));
    }
Behavior2/5

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

No annotations are provided, so the description must cover behavioral traits. It mentions entry/exit prices and hold duration but fails to disclose data freshness, rate limits, or any side effects. This is a significant gap.

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 concise with four sentences: purpose, general output, filterability, and specific use cases. It is front-loaded and every sentence is informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 and the presence of 7 optional parameters, the description lacks details on the exact output structure (beyond mentioning price and duration). It is adequate for basic use but not fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with clear parameter descriptions. The tool description adds value by linking parameters to concrete use cases (e.g., maxDuration=1000 for sub-second trades), which aids selection and invocation.

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 recently closed positions across all traders, with specific filtering options. It distinguishes from sibling tools like pulse_trader_closed_positions by emphasizing the aggregate scope.

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 explicit use cases with filter examples (e.g., maxDuration=1000 for HFT trades, minNotional=100000 for large positions). It does not explicitly state when not to use, but the use cases are clear.

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