Skip to main content
Glama

Customer LTV and CAC

bpj_customer_ltv_cac
Read-onlyIdempotent

Estimate contribution LTV and acquisition payback assuming constant monthly churn, revenue, and gross margin.

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": {
      "monthlyRevenue": "<monthlyRevenue>",
      "margin": "<margin>",
      "churn": "<churn>",
      "acquisitionCost": "<acquisitionCost>"
    },
    "name": "bpj_customer_ltv_cac"
  }
}

Input Schema

NameRequiredDescriptionDefault
churnYes
marginYes
monthlyRevenueYes
acquisitionCostYes

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?

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the description's real contribution is disclosing that the model assumes constant churn, constant revenue, and constant margin, meaning no cohort decay curves or discounting are modeled. It stops short of saying what the response contains or that payback can be infinite/never when margin times revenue does not cover churn.

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?

A single front-loaded sentence with no filler: the verb, the two outputs, and the assumption set all appear in order. Nothing is padded or repeated from the schema.

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?

Given that four required numeric parameters are all present, the description covers what the tool computes and under what assumptions. The remaining gap is that with no output schema, the agent is not told the shape of the result, such as the units or whether payback is expressed in months.

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%, so only the field titles ('Monthly churn %', 'Gross margin %', etc.) convey meaning. The description adds the key constraint that these inputs are held constant, but it does not resolve whether churn and margin are entered as percent numbers or fractions, nor how margin feeds into 'contribution' LTV, leaving a real ambiguity for four required parameters.

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 pairs the specific verb 'Estimate' with two named outputs, 'contribution LTV' and 'acquisition payback', and states the modeling assumptions behind them. It does not distinguish itself from other finance calculators such as bpj_cash_runway or bpj_break_even_units, but the verb and resource are unambiguous.

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?

No explicit when-to-use or when-not-to-use guidance is given, and no alternative tool is named. Usage is only implied by the calculation being described, which is adequate for a self-contained estimator but leaves the agent to infer when this beats a sibling financial tool.

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.