Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official
by Coinversaa
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

Recent-Tier Cohort Lifecycle Stats

pulse_cohort_recent_lifecycle_stats
Read-onlyIdempotent

Analyze per-wallet lifecycle stats for a last-30-day tier cohort, covering wins, losses, liquidations, total PnL, fees, and average hold. Identify which wallets are currently profitable via position-level metrics.

Instructions

Per-wallet lifecycle stats for a cohort defined by its LAST-30-DAY tier: lifecycles, wins, losses, liquidations, total PnL, fees, avg hold, biggest win/loss, plus the wallet's recent pnl/size tier labels. Use for position-level analysis of who is currently printing.

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 wallets to return.
offsetNoPagination offset.
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. Dates show when Glama detected each change.

  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/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior, so the description does not need to restate those. It adds useful behavioral context beyond the schema by explaining the cohort is based on LAST-30-DAY tier and outlining the returned wallet-level metrics. No contradiction with 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?

The description is compact and front-loaded, leading with the core resource definition and metric list, then closing with a clear use case. Every phrase earns its place; there is no filler or redundant restatement of the tool name.

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?

With no output schema, the description carries responsibility for explaining what the agent should expect in the response, and it does a solid job by enumerating the returned metrics and tying them to the cohort definition. It is not exhaustive—ordering and default toon-format behavior are left to the schema—but it is sufficient for correct tool selection.

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 adds some contextual meaning around 'recent tier' and 'currently printing,' but it does not substantially extend the already detailed parameter documentation for tier, tierType, limit, offset, 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 clearly states the resource: per-wallet lifecycle stats for a cohort defined by its LAST-30-DAY tier, and lists the included metrics such as lifecycles, wins, losses, liquidations, total PnL, fees, and avg hold. It conveys a distinct scope from sibling lifecycle/cohort tools, though it does not explicitly name an alternative.

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 explicitly says 'Use for position-level analysis of who is currently printing,' which gives the agent a clear decision signal for when to invoke this tool. It does not mention exclusions or when-not-to-use cases, so it stops short of a full 5.

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