Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official

pulse_cohort_positions

Retrieve real-time positions held by a specific trader cohort, such as top PnL or size tiers, for instant whale intelligence.

Instructions

See what a specific trader cohort is holding RIGHT NOW. For example, get all live positions held by 'money_printer' tier traders or 'leviathan' size wallets. This is real-time whale intelligence.

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
limitNoNumber of positions to return

Implementation Reference

  • src/index.ts:404-420 (registration)
    Registration of the pulse_cohort_positions tool. It registers a tool that fetches live positions held by a specific trader cohort (by PnL or size tier).
    // ══════════════════════════════════════════════════════════
    // TOOL 6: Cohort Positions (What whales are doing NOW)
    // ══════════════════════════════════════════════════════════
    if (shouldRegister("pulse_cohort_positions")) server.registerTool(
      "pulse_cohort_positions",
      {
        description: "See what a specific trader cohort is holding RIGHT NOW. For example, get all live positions held by 'money_printer' tier traders or 'leviathan' size wallets. This is real-time whale intelligence.",
        inputSchema: {
          useToonFormat: useToonFormatSchema,
          tierType: z.enum(["pnl", "size"]).describe("Tier category: 'pnl' for profit tiers, 'size' for volume tiers"),
          tier: tierSchema,
          limit: z.number().min(1).max(200).default(50).describe("Number of positions to return"),
        },
      },
      async ({ useToonFormat, tierType, tier, limit }) =>
        toolResult(await callAPI(useToonFormat, `/pulse/cohorts/${tierType}/${tier}/positions`, { limit: String(limit) }))
    );
  • Handler for pulse_cohort_positions. Calls the external API at /pulse/cohorts/{tierType}/{tier}/positions with a limit parameter, passing useToonFormat to optionally encode the result in toon format.
    async ({ useToonFormat, tierType, tier, limit }) =>
      toolResult(await callAPI(useToonFormat, `/pulse/cohorts/${tierType}/${tier}/positions`, { limit: String(limit) }))
  • Input schema for pulse_cohort_positions: accepts useToonFormat (boolean), tierType (enum 'pnl'|'size'), tier (enum from tierSchema), and limit (number 1-200, default 50).
    inputSchema: {
      useToonFormat: useToonFormatSchema,
      tierType: z.enum(["pnl", "size"]).describe("Tier category: 'pnl' for profit tiers, 'size' for volume tiers"),
      tier: tierSchema,
      limit: z.number().min(1).max(200).default(50).describe("Number of positions to return"),
    },
Behavior3/5

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

With no annotations, the description indicates a read operation ('see...holding') but does not disclose data freshness, caching, rate limits, or output behavior beyond format selection. The 'real-time' claim is stated but not elaborated.

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 front-load the purpose and an example, with no redundant information. Every word serves function.

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 tool's straightforward purpose and rich schema, the description is nearly complete. It lacks details on return values (no output schema) and could briefly mention that this is for current, not historical, holdings, but overall sufficient.

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?

Input schema has 100% coverage, so the description adds limited value. It reinforces tier examples from the schema but does not explain parameter interactions or provide new constraints. 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 the tool's purpose: 'See what a specific trader cohort is holding RIGHT NOW.' It provides concrete examples (money_printer, leviathan) and distinguishes it from sibling tools like pulse_cohort_trades or pulse_cohort_bias, which focus on trades or bias rather than live positions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for real-time whale intelligence but does not explicitly compare to alternatives like pulse_cohort_bias (sentiment) or pulse_cohort_trades (historical trades). No when-not-to-use guidance is provided, leaving the agent to infer context.

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