Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official
by Coinversaa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Cohort Trades

pulse_cohort_trades
Read-onlyIdempotent

View recent trades for any trader cohort on Hyperliquid. Filter by profitability or size tier and time window to trace behavior across individual positions.

Instructions

See every trade a specific cohort has made recently. For example: 'show me all trades the apex (Apex) tier made in the last hour.'

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 trades to return
sinceNoTime window: e.g. '10m' (minutes), '1h' (hours), '1d' (days)1h
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.5/5.0
Behavior2/5

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

With readOnlyHint true the safety profile is already clear, but the description's claim of 'every trade' is contradicted by the schema's limit parameter (max 100, default 50), so it can mislead an agent about completeness of results. It also does not disclose the default compact toon format or that results are bounded by the since window.

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 short sentences state the purpose and give a concrete usage example with no filler. The structure front-loads the action and then illustrates it productively.

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?

The rich schema plus readOnly/idempotent annotations make the tool callable, and the example clarifies the tier/time intent. However, the description omits the bounded limit behavior (undermining 'every trade'), and with no output schema it does not set expectations for the returned trade fields or toon format.

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?

The schema covers 100% of parameters with descriptions, so the description does not need to carry the semantic load. It reinforces the tier and time-window concepts through the apex example, but adds nothing about tierType or limit beyond what the schema already provides.

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 clearly identifies a read operation that lists recent trades for a chosen cohort, with a concrete 'apex tier' example that anchors the resource and time scope. It does not explicitly differentiate from the similarly named sibling pulse_cohort_recent_trades, so it stops short of the highest clarity bar.

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 example ('show me all trades the apex tier made in the last hour') gives a clear context for when to invoke the tool and how to phrase a request. It does not state when-not-to-use or point to alternatives such as pulse_trader_trades or pulse_recent_trades, but the intended use is reasonably clear.

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