Skip to main content
Glama

Scale Paid Check

scale_paid_check
Read-only

Decide whether to scale paid now by analyzing customer cohorts, churn reasons, stop rates, payback, and unit economics; return scale, capped-test, or hold recommendations per segment.

Instructions

Helps you decide whether to scale paid now: it takes your customer list (signing date, segment, monthly fee and any stop or return dates) and your churn reasons, and returns, for each customer group, scale, run a capped test, or hold, with the counts behind it, the stop rule, payback, a first draft response to each churn reason and a churn interview guide. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing required fields or invalid values return an error naming what to supply or correct. Use this instead of pmf_scorecard when you need a paid-growth decision grounded in customer cohorts and unit economics.

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": {
      "product": "<product>",
      "business_model": "<business_model>",
      "billing_term": "<billing_term>",
      "as_of": "<as_of>",
      "customers": "<customers>",
      "churn_reasons": "<churn_reasons>",
      "interview_persona": "<interview_persona>"
    },
    "name": "scale_paid_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofYesThe date the list was pulled (YYYY-MM-DD). Format is text in YYYY-MM-DD form. For example, "2026-11-17".
metricsNoOptional: each metric with its name, value, whether it counts customers or revenue, and its period. Format is a JSON array. For example, [{"name":"an approved anonymous manufacturer","value":12}].
productYesProduct in one line. Format is text. For example, "invoice review service".
paid_cacNoOptional: paid-only CAC. Format is a JSON number. For example, 24000.
test_capNoOptional: all-in budget for a capped test. Format is a JSON number. For example, 12.
customersYesOne row per customer (1 to 2000 items). Format is a JSON array. For example, [{"id":"account-001","signed":"2026-11-17","segment":"manufacturers with 200 to 500 employees","monthly_fee":24000}].
stop_lineNoOptional (default 0.80): share of a cohort that must still pay at month 12. 0.80 is Shashwat's example line for a $36,000 contract, not a benchmark. Format is a JSON number.
blended_cacNoOptional: blended CAC, shown for contrast only. Format is a JSON number. For example, 24000.
billing_termYesHow customers are billed. Format is text using one of the listed labels. For example, "monthly".
gross_marginNoOptional (0 to 1): gross margin needed for the money section. Format is a JSON number. For example, 0.8.
churn_reasonsYesReasons in customers' words, comma or line separated. Format is text. For example, "implementation delays and unclear ownership".
business_modelYesBusiness model, passed on to retention_playbook. Format is text using one of the listed labels. For example, "saas_subscription".
win_rate_floorNoOptional (0 to 1): a win rate the buyer is confident paid can reach. Format is a JSON number. For example, 0.8.
win_rate_targetNoOptional (0 to 1): the highest win rate the buyer would believe. Format is a JSON number. For example, 0.8.
interview_personaYesRole to interview, for the interview kit. Format is text. For example, "finance director".
payback_line_monthsNoOptional (default 12): the longest acceptable paid payback in months. 12 is Shashwat's example line for a $36,000 contract, not a benchmark. Format is a JSON number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.25

TDQS

A4.4/5.0
Behavior5/5

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

Goes well past the annotations: no sign-in required, no inputs or outputs stored, hosted usage metadata recorded, and errors on missing required fields or invalid values explicitly name what to supply. Annotations already cover read-only/non-destructive/non-open-world, so these additions are the real value — auth, data retention, and failure behavior are all disclosed.

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?

Front-loaded with the decision and inputs, then outputs, then operational facts, then the sibling hand-off — a sensible order with no filler sentences. It is dense and packs several distinct claims into one long opening sentence, which slightly hurts scannability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 16-parameter analytical tool with no output schema, the description carries the necessary burden: it enumerates the returned artifacts, states error semantics, and covers privacy/auth. Combined with a fully documented input schema, an agent has everything needed to call it and interpret the result.

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 baseline is 3. The description paraphrases the customer row fields (signing date, segment, monthly fee, stop/return dates) already documented in the schema, but says nothing about the several optional economics parameters (paid_cac, blended_cac, test_cap, win_rate_floor/target, gross_margin, stop_line, payback_line_months) or how they alter the recommendation.

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?

States a specific decision verb ('decide whether to scale paid now'), the exact inputs consumed (customer list with signing date, segment, monthly fee, stop/return dates, plus churn reasons), and the concrete per-cohort output (scale / capped test / hold with counts, stop rule, payback, draft responses, interview guide). This is unambiguous enough to separate from siblings without opening a schema.

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?

Explicitly routes the agent: 'Use this instead of pmf_scorecard when you need a paid-growth decision grounded in customer cohorts and unit economics.' That names an alternative and the selecting condition. It stops short of stating when-not to use it against the other siblings (retention_playbook, customer_interview_kit, segment_and_seat_cut_check), which overlap conceptually with the churn and interview outputs.

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