Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official
by Coinversaa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Cohort History

pulse_cohort_history
Read-onlyIdempotent

Track daily PnL, trade count, and activity for a trader tier over time to identify performance trends and shifts in behavior.

Instructions

Get historical performance data for a specific trader cohort over time. Shows how a tier's aggregate PnL, trade count, and activity have changed day-by-day. Use to spot trends like 'the sharps (Sharps) tier has been increasingly bearish over the last month.'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoNumber of days of history to return
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.
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.6.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint, idempotentHint, non-destructive), so the description's burden is lower. It adds useful context that data is historical, tier-level, and day-by-day, but does not disclose output shape, pagination, or any additional behavioral caveats.

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 no filler. It front-loads the verb-resource pair, then details the metrics and granularity, then gives a concrete use case. 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?

Given strong annotations and full schema coverage of all parameters, the description is largely complete for selecting and invoking the tool. It conveys the data returned and a representative use case; the main omission is guidance on choosing between this and closely related cohort-history siblings.

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 loosely references a 'trader cohort' and 'tier', but does not add meaning beyond what the schema already documents for tierType, tier, days, or useToonFormat.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Get historical performance data for a specific trader cohort over time.' It also names concrete metrics (aggregate PnL, trade count, activity) and day-by-day granularity. However, it does not explicitly differentiate itself from close siblings like pulse_cohort_performance_daily or pulse_cohort_bias_history.

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 'Use to spot trends...' sentence provides a clear, concrete usage scenario with an illustrative example. It does not, however, state when not to use this tool or name alternatives, so it stops short of full routing 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