Skip to main content
Glama

Customer Cohort Survival

bpj_customer_logo_survival
Read-onlyIdempotent

Apply observed one-month account churn to project survivors of the same starting cohort at a constant rate.

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": {
      "start": "<start>",
      "lost": "<lost>",
      "months": "<months>"
    },
    "name": "bpj_customer_logo_survival"
  }
}

Input Schema

NameRequiredDescriptionDefault
lostYes
startYes
monthsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

The supplied annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description does add one real behavioral fact, that churn is applied at a constant rate to the same starting cohort, but says nothing about what is returned, whether results are a scalar or a series, or rounding behavior, and no output schema fills that gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence with no filler, and the core mechanism is stated up front. It is slightly over-packed, stacking churn source, cohort, and constant-rate assumption into a single clause chain that takes a second read to parse.

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?

For a three-required-parameter calculation tool with no output schema, an agent still lacks the return shape (single survivor count vs. per-month series) and the meaning of edge cases such as lost exceeding start. The assumptions are named, which is the strongest part, but the definition stops short of being fully self-sufficient.

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 0%, so the description has to carry the load. It implicitly explains the relationship between opening accounts, lost accounts, and the horizon via "one-month account churn" and "project," which helps, but it never explicitly ties these to the start, lost, and months parameters or states units and edge behavior.

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 uses a specific verb-plus-resource construction ("project survivors of the same starting cohort") and clarifies that "logo" here means accounts experiencing churn. The purpose is intelligible without opening the schema, although the phrasing is dense and does not contrast it with the other customer-cohort siblings.

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?

Usage is only implied: the description frames the scenario (applying observed one-month churn forward) but never says when to choose this over alternatives such as bpj_experiment_cohort_allocation or bpj_customer_ltv_cac, and lists no exclusions. An agent can infer the intended case but receives no explicit routing 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.