Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official
by Coinversaa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Recent-Tier Cohort Positions

pulse_cohort_recent_positions
Read-onlyIdempotent

Get live positions for cohorts defined by trailing 30-day profitability or volume tiers. See what currently-active wallets hold right now to detect regime changes that all-time snapshots overlook.

Instructions

Live positions held by a cohort defined by its LAST-30-DAY tier (pnl_tier_recent / size_tier_recent), not lifetime tier. Surfaces what currently-printing wallets are positioned for right now — catches regime changes the all-time pulse_cohort_positions misses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tierYesTier slug. PnL tiers (by profitability): apex (Apex), sharps (Sharps), grinders (Grinders), scrapers (Scrapers), crowd (The Crowd), bleeders (Bleeders), trapped (Trapped), blown_out (Blown Out). Size tiers (by volume): heavyweights (Heavyweights), cruiserweights (Cruiserweights), middleweights (Middleweights), welterweights (Welterweights), lightweights (Lightweights), featherweights (Featherweights), flyweights (Flyweights), strawweights (Strawweights). Legacy slugs (money_printer, smart_money, grinder, humble_earner, exit_liquidity, semi_rekt, full_rekt, giga_rekt, leviathan, tidal_whale, whale, small_whale, apex_predator, dolphin, fish, shrimp) remain accepted; API responses still emit legacy slugs.
limitNoNumber of positions to return.
tierTypeYesTier category: 'pnl' for profit tiers, 'size' for volume tiers.
useToonFormatNoReturn data in compact toon format (default: true). Set to false for standard JSON.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.10.0
    • changedInput schema / properties / tier / description
      Previous value: -"Tier 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"New value: +"Tier slug. PnL tiers (by profitability): apex (Apex), sharps (Sharps), grinders (Grinders), scrapers (Scrapers), crowd (The Crowd), bleeders (Bleeders), trapped (Trapped), blown_out (Blown Out). Size tiers (by volume): heavyweights (Heavyweights), cruiserweights (Cruiserweights), middleweights (Middleweights), welterweights (Welterweights), lightweights (Lightweights), featherweights (Featherweights), flyweights (Flyweights), strawweights (Strawweights). Legacy slugs (money_printer, smart_money, grinder, humble_earner, exit_liquidity, semi_rekt, full_rekt, giga_rekt, leviathan, tidal_whale, whale, small_whale, apex_predator, dolphin, fish, shrimp) remain accepted; API responses still emit legacy slugs."
    • changedInput schema / properties / tier / enum
      Previous value: -[
-  "money_printer",
-  "smart_money",
-  "grinder",
-  "humble_earner",
-  "exit_liquidity",
-  "semi_rekt",
-  "full_rekt",
-  "giga_rekt",
-  "leviathan",
-  "tidal_whale",
-  "whale",
-  "small_whale",
-  "apex_predator",
-  "dolphin",
-  "fish",
-  "shrimp"
-]New value: +[
+  "apex",
+  "sharps",
+  "grinders",
+  "scrapers",
+  "crowd",
+  "bleeders",
+  "trapped",
+  "blown_out",
+  "heavyweights",
+  "cruiserweights",
+  "middleweights",
+  "welterweights",
+  "lightweights",
+  "featherweights",
+  "flyweights",
+  "strawweights",
+  "money_printer",
+  "smart_money",
+  "grinder",
+  "humble_earner",
+  "exit_liquidity",
+  "semi_rekt",
+  "full_rekt",
+  "giga_rekt",
+  "leviathan",
+  "tidal_whale",
+  "whale",
+  "small_whale",
+  "apex_predator",
+  "dolphin",
+  "fish",
+  "shrimp"
+]
  2. Addedv0.8.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already disclose that this is read-only, open-world, idempotent, and non-destructive. The description adds that the data is 'live' and scoped to recent-tier cohorts, which is useful, but it does not disclose return formatting, pagination behavior, or data-freshness caveats. Since annotations carry the safety profile, this is adequate but not exceptional.

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 tight sentences with no filler. The first sentence states the defining behavior and scope, and the second gives the practical use case and contrasts it with the sibling tool. Every sentence earns its place.

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?

The tool has only two required parameters, full schema descriptions, and clear annotations. The description covers the non-obvious selection logic that distinguishes this from pulse_cohort_positions. There is no output schema, but the return concept ('positions held by a cohort') is clear enough for an agent to invoke the tool correctly.

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%, and the schema fully documents all four parameters including enums, defaults, and legacy-slug behavior. The description adds the recent-tier concept (pnl_tier_recent / size_tier_recent), but the schema already handles parameter semantics, so the 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 names a specific resource ('positions held by a cohort') and a specific defining scope ('LAST-30-DAY tier'), and explicitly contrasts it with the all-time pulse_cohort_positions sibling. An agent can immediately tell what this tool returns and how it differs from related cohort-position tools.

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

Usage Guidelines5/5

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

The description explicitly states the selection criterion ('LAST-30-DAY tier ... not lifetime tier') and names the alternative it complements ('the all-time pulse_cohort_positions misses'). This gives clear when-to-use and when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools