Skip to main content
Glama

Retention Offer Lift Value

bpj_retention_offer_lift_value
Read-onlyIdempotent

Compare expected horizon revenue with and without a temporary discount using the probability of staying for the full horizon.

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": {
      "saved": "<saved>",
      "months": "<months>",
      "discountMonths": "<discountMonths>",
      "concession": "<concession>",
      "baseline": "<baseline>",
      "treated": "<treated>"
    },
    "name": "bpj_retention_offer_lift_value"
  }
}

Input Schema

NameRequiredDescriptionDefault
savedYes
monthsYes
treatedYes
baselineYes
concessionYes
discountMonthsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare this is a read-only, idempotent, non-destructive calculation, so the safety profile is covered. The description adds that the computation is a two-scenario revenue comparison over a horizon, but it does not state the return shape, sign convention for lift, or units of the result — which matters for a calculation tool with no 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.

Conciseness4/5

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

A single front-loaded sentence with no filler. It is well-structured but arguably too terse for a six-parameter calculation tool, leaving room that parameter explanation could have used.

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?

Read-only annotations cover the safety story, but with six required undocumented parameters and no output schema, the description leaves the agent guessing about input roles and return values. It conveys the high-level concept but not enough to call the tool confidently with correct inputs.

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

Parameters2/5

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

Schema description coverage is 0% and all six parameters are required, so the description carries full burden; it only loosely gestures at discount duration and retention probability. It never explains the distinction between 'concession' (discount %) and 'discountMonths', or what 'saved' (retained account monthly price) and 'baseline'/'treated' percentages mean in the calculation.

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 names a specific operation (compare expected horizon revenue with and without a temporary discount) and the mechanism used (probability of staying for the full horizon). It is clearer than a tautology, but it does not differentiate this from sibling value/lift tools such as bpj_exchange_offer_increment or bpj_geo_control_adjusted_lift.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus alternatives, nor any stated prerequisites or exclusions. The implied context is comparing a retention offer against a baseline, but the agent must infer that entirely.

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.