Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official

pulse_cohort_trades

Retrieve recent trades made by a specific trader cohort (e.g., money_printer, whale) on Hyperliquid. Filter by time window and tier type to analyze real-time alpha from on-chain activity.

Instructions

See every trade a specific cohort has made recently. For example: 'show me all trades the money_printer tier made in the last hour.' This is real-time alpha — nobody else has this data as an API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
useToonFormatNoReturn data in compact toon format (default: true). Set to false for standard JSON.
tierTypeYesTier category: 'pnl' for profit tiers, 'size' for volume tiers
tierYesTier name. PnL tiers: money_printer, smart_money, grinder, humble_earner, exit_liquidity, semi_rekt, full_rekt, giga_rekt. Size tiers: leviathan, tidal_whale, whale, small_whale, apex_predator, dolphin, fish, shrimp
sinceNoTime window: e.g. '10m' (minutes), '1h' (hours), '1d' (days)1h
limitNoNumber of trades to return

Implementation Reference

  • src/index.ts:527-542 (registration)
    Registration of the pulse_cohort_trades tool using server.registerTool(). It is not in the FREE_TIER_TOOLS set (line 30-38), so it requires an API key.
    // ══════════════════════════════════════════════════════════
    if (shouldRegister("pulse_cohort_trades")) server.registerTool(
      "pulse_cohort_trades",
      {
        description: "See every trade a specific cohort has made recently. For example: 'show me all trades the money_printer tier made in the last hour.' This is real-time alpha — nobody else has this data as an API.",
        inputSchema: {
          useToonFormat: useToonFormatSchema,
          tierType: z.enum(["pnl", "size"]).describe("Tier category: 'pnl' for profit tiers, 'size' for volume tiers"),
          tier: tierSchema,
          since: sinceSchema.default("1h"),
          limit: z.number().min(1).max(100).default(50).describe("Number of trades to return"),
        },
      },
      async ({ useToonFormat, tierType, tier, since, limit }) =>
        toolResult(await callAPI(useToonFormat, `/pulse/cohorts/${tierType}/${tier}/trades`, { since, limit: String(limit) }))
    );
  • Handler function for pulse_cohort_trades: calls the API endpoint /pulse/cohorts/{tierType}/{tier}/trades with 'since' and 'limit' query parameters.
    async ({ useToonFormat, tierType, tier, since, limit }) =>
      toolResult(await callAPI(useToonFormat, `/pulse/cohorts/${tierType}/${tier}/trades`, { since, limit: String(limit) }))
  • Input schema for pulse_cohort_trades: expects useToonFormat (boolean), tierType (enum: pnl/size), tier (tierSchema enum), since (time window regex), and limit (number 1-100).
    {
      description: "See every trade a specific cohort has made recently. For example: 'show me all trades the money_printer tier made in the last hour.' This is real-time alpha — nobody else has this data as an API.",
      inputSchema: {
        useToonFormat: useToonFormatSchema,
        tierType: z.enum(["pnl", "size"]).describe("Tier category: 'pnl' for profit tiers, 'size' for volume tiers"),
        tier: tierSchema,
        since: sinceSchema.default("1h"),
        limit: z.number().min(1).max(100).default(50).describe("Number of trades to return"),
      },
  • build/index.js:362-374 (registration)
    Compiled JS registration of the pulse_cohort_trades tool (mirrors src/index.ts implementation).
    // TOOL 13: Cohort Recent Trades
    // ══════════════════════════════════════════════════════════
    if (shouldRegister("pulse_cohort_trades"))
        server.registerTool("pulse_cohort_trades", {
            description: "See every trade a specific cohort has made recently. For example: 'show me all trades the money_printer tier made in the last hour.' This is real-time alpha — nobody else has this data as an API.",
            inputSchema: {
                useToonFormat: useToonFormatSchema,
                tierType: z.enum(["pnl", "size"]).describe("Tier category: 'pnl' for profit tiers, 'size' for volume tiers"),
                tier: tierSchema,
                since: sinceSchema.default("1h"),
                limit: z.number().min(1).max(100).default(50).describe("Number of trades to return"),
            },
        }, async ({ useToonFormat, tierType, tier, since, limit }) => toolResult(await callAPI(useToonFormat, `/pulse/cohorts/${tierType}/${tier}/trades`, { since, limit: String(limit) })));
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only promotes the data as 'real-time alpha' but offers no technical behavioral details such as authentication requirements, rate limits, or error handling. This is insufficient for a tool with no 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?

Two sentences: the first states purpose, the second provides an example and value proposition. No filler, front-loaded, every sentence earns its place.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 5 parameters, no output schema, and no annotations, the short description does not cover return format, pagination, or behavior when no trades exist. More information is needed for complete 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 the baseline is 3. The description does not add any additional meaning beyond what the schema already documents for each parameter.

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 'see' and resource 'every trade a specific cohort has made recently', with a concrete example. It distinguishes from sibling tools like pulse_cohort_summary or pulse_cohort_positions by focusing on trades.

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 a clear usage context with an example, suggesting when to use the tool (for recent cohort trades). However, it does not explicitly state when not to use it or mention alternatives, though sibling context implies differentiation.

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