Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official
by Coinversaa
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

Recent-Tier Cohort Alpha Concentration

pulse_cohort_recent_alpha_concentration
Read-onlyIdempotent

Measure profit concentration within a recent-tier cohort: percentile bands, wallet counts, band PnL, and % of tier PnL. Answers whether a few wallets carry most of the cohort's PnL.

Instructions

How concentrated profit is WITHIN a recent-tier cohort: percentile bands of the cohort's wallets and each band's share of the cohort's total PnL. Returns band, wallet count, band PnL, % of tier PnL, and tier total wallets. Use for 'within the hot apex (Apex) cohort, do a few wallets carry everything?'.

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

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

Annotations already establish this as read-only, idempotent, and non-destructive. The description adds useful behavioral detail beyond annotations by explaining that it segments wallets into percentile bands and returns their PnL concentration, including band PnL, wallet count, percentage of tier PnL, and total tier wallets. This effectively conveys the tool's output behavior without an output schema.

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 two tight sentences followed by a concrete use-case quote. It front-loads the core behavior, lists return fields, and gives an example without any filler or repetition of schema content.

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 description is complete enough for a read-only aggregation tool: it defines the analysis, lists returned fields, provides a usage example, and all input parameters are fully documented in the schema. Minor gaps such as the definition of 'recent' and percentile-band boundaries are not critical 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%, so the schema already documents tierType, tier, and useToonFormat in detail. The description adds no additional parameter-level meaning beyond referencing the Apex tier as an example. Baseline 3 is appropriate because the structured schema carries the parameter documentation burden.

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 states a specific analytical purpose: measuring profit concentration within a recent-tier cohort via percentile bands and their share of cohort PnL. It also enumerates the exact returned fields and gives a concrete example use case, making it clearly distinguishable from sibling cohort and market-concentration tools.

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 provides explicit usage context via the quote: 'within the hot apex (Apex) cohort, do a few wallets carry everything?' This tells an agent when to reach for the tool. It does not name alternative tools or give exclusion criteria, so it stops short of a full when-not/alternatives guide.

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