Skip to main content
Glama

BRAINIAC Predictive & Customer Analytics

Cohort retention matrix and weighted curve

predictive-analytics_cohort-retention
Read-onlyIdempotent

Build day/week/month cohort retention in classic or rolling mode from signup and activity dates, with partial-period flags and a size-weighted curve. Price $0.03 USDC. POST /api/v1/predictive-analytics/cohort-retention. An unpaid call returns the x402 payment terms and does not run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "events": "<events>",
      "asOf": "<asOf>"
    },
    "name": "predictive-analytics_cohort-retention"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfYesasOf, string. Required.
modeNomode, string, one of classic, rolling. Required.classic
eventsYesevents, array. Required.
periodNoperiod, string, one of day, week, month. Required.month
timezoneNotimezone, string, length 1 to 64. Required.UTC

Output Schema

NameRequiredDescriptionDefault
cohortsNocohorts. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.
weightedCurveNoweightedCurve. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive, open-world behavior, but the description adds meaningful operational context: pricing at $0.03 USDC, the POST endpoint, and the crucial fact that an unpaid call returns x402 payment terms without running. It also notes partial-period flags and a size-weighted curve, though it does not cover authentication details beyond payment.

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 compact sentences, front-loading the core operation before price, endpoint, and unpaid-call behavior. Every sentence adds relevant information without repetition or filler.

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?

An output schema exists, so return values need not be explained, and the description covers the analytical modes, time periods, output shape cues, and payment behavior. Given the tool's moderate complexity, it is largely complete, with only minor gaps around failure modes or permissions beyond payment.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents each parameter thoroughly. The description still adds semantic meaning by tying events to signup and activity dates and by framing mode and period as cohort-retention construction choices, which helps an agent understand how the parameters combine.

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 states a specific verb and resource: build a cohort retention matrix and weighted curve from signup and activity dates. It clearly distinguishes itself from the other predictive-analytics siblings by naming cohort retention, but it does not explicitly contrast with adjacent analyses such as survival or CLV tools.

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

Usage Guidelines3/5

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

It implies usage by describing the required inputs (signup and activity dates) and the available classic/rolling and day/week/month options, but it does not state when to prefer this tool over alternatives or any exclusions. The payment note is contextual rather than usage guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources