Skip to main content
Glama

PMF Scorecard

pmf_scorecard
Read-only

Assess product-market fit and decide whether to scale by scoring product, market, and metrics against benchmark ranges. Get priority actions, data gaps, and customer feedback insights.

Instructions

Helps you decide whether you have product market fit and whether to scale: it takes your product, target market and current metrics (MRR, ACV, churn, NPS, CAC, LTV, retention, activation and similar) and returns a scorecard that scores each dimension against example benchmark ranges. It also gives priority actions and the data gaps to fill, reads the business model from your inputs, leaves the activation score out for services, connectivity and investment businesses, and quotes and answers your customer feedback. 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 scale_paid_check when you need a broad PMF assessment against the tool's example benchmarks.

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>",
      "target_market": "<target_market>",
      "current_metrics": "<current_metrics>"
    },
    "name": "pmf_scorecard"
  }
}

Input Schema

NameRequiredDescriptionDefault
productYesProduct name and brief description. Format is text. For example, "invoice review service".
your_sectorNoOptional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear. Format is text using one of the listed labels. For example, "logistics_tech".
target_marketYesBenchmark segment for scoring (for example enterprise SaaS, telecom or logistics tech). Ask the user to confirm it when it differs from the product description. The selected benchmark and its stated fallback ranges are used; the output explains conflicts. The separate sector choice controls sector notes. Format is text using one of the listed labels.
business_modelNoOptional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other inputs and says how it read it. Format is text using one of the listed labels. For example, "saas".
time_in_marketNoHow long the product has been in market (shown in the scorecard). Format is text using one of the listed labels. For example, "pre_launch".
current_metricsYesYour current metrics, written as text (the tool reads the figures from it). Include any of: MRR, ARR, ACV, churn rate, NPS, CAC, LTV, retention rate, activation rate, DAU/MAU, trial conversion, revenue growth. Example: 'MRR: $50K, Churn: 3%, NPS: 45, CAC: $500, LTV: $3000, Retention: 92%'. A figure that no rule scores is listed as not scored. Format is text.
customer_feedbackNoOptional: Qualitative feedback themes, one per line or separated by semicolons (for example 'Customers like X; they struggle with Y'). Each theme is quoted and answered. Format is text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv2.2.25
    • addedInput schema / properties / business_model
      Added value: +{
      +  "description": "Optional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other inputs and says how it read it. Format is text using one of the listed labels. For example, \"saas\".",
      +  "enum": [
      +    "saas",
      +    "services",
      +    "connectivity",
      +    "transactions",
      +    "marketplace",
      +    "hardware_software",
      +    "investment"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / current_metrics / description
      Previous value: -"Key metrics: MRR, churn, NPS, CAC, LTV, growth rate"New value: +"Your current metrics, written as text (the tool reads the figures from it). Include any of: MRR, ARR, ACV, churn rate, NPS, CAC, LTV, retention rate, activation rate, DAU/MAU, trial conversion, revenue growth. Example: 'MRR: $50K, Churn: 3%, NPS: 45, CAC: $500, LTV: $3000, Retention: 92%'. A figure that no rule scores is listed as not scored. Format is text."
    • changedInput schema / properties / customer_feedback / description
      Previous value: -"Qualitative insights from customers"New value: +"Optional: Qualitative feedback themes, one per line or separated by semicolons (for example 'Customers like X; they struggle with Y'). Each theme is quoted and answered. Format is text."
    • changedInput schema / properties / product / description
      Previous value: -"Product/service name and brief description"New value: +"Product name and brief description. Format is text. For example, \"invoice review service\"."
    • changedInput schema / properties / target_market / description
      Previous value: -"Specific market segment you're targeting"New value: +"Benchmark segment for scoring (for example enterprise SaaS, telecom or logistics tech). Ask the user to confirm it when it differs from the product description. The selected benchmark and its stated fallback ranges are used; the output explains conflicts. The separate sector choice controls sector notes. Format is text using one of the listed labels."
    • addedInput schema / properties / target_market / enum
      Added value: +[
      +  "enterprise_saas",
      +  "smb_saas",
      +  "consumer",
      +  "marketplace",
      +  "fintech",
      +  "logistics_tech",
      +  "vertical_saas",
      +  "ai_native",
      +  "ites",
      +  "telecom",
      +  "software",
      +  "cybersecurity",
      +  "other"
      +]
    • changedInput schema / properties / time_in_market / description
      Previous value: -"How long since launch"New value: +"How long the product has been in market (shown in the scorecard). Format is text using one of the listed labels. For example, \"pre_launch\"."
    • addedInput schema / properties / time_in_market / enum
      Added value: +[
      +  "pre_launch",
      +  "0_6_months",
      +  "6_12_months",
      +  "1_2_years",
      +  "2_plus_years"
      +]
    • addedInput schema / properties / your_sector
      Added value: +{
      +  "description": "Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear. Format is text using one of the listed labels. For example, \"logistics_tech\".",
      +  "enum": [
      +    "logistics_tech",
      +    "fintech",
      +    "saas",
      +    "vertical_saas",
      +    "ai_native",
      +    "ites",
      +    "telecom",
      +    "software",
      +    "cybersecurity",
      +    "other"
      +  ],
      +  "type": "string"
      +}
  2. First observedv1.0.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the read-only/no-destruction profile, but the description adds materially more: no sign-in required, no storage of inputs or outputs, hosted usage metadata recorded, and invalid input returns an error naming what to supply or correct. It also discloses conditional logic — the activation score is omitted for services, connectivity and investment businesses, and the business model is inferred from inputs when not supplied.

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 the tool supports, and every clause carries information — privacy, errors, conditional scoring, sibling routing. It is dense, however: the opening sentence strings together five or six distinct behaviors, which makes scanning harder than a short bulleted or segmented phrasing would.

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?

No output schema exists, and the description compensates by describing what comes back — per-dimension scores against benchmark ranges, priority actions, and data gaps to fill. Combined with privacy, error, and conditional-scoring disclosure, nothing an agent needs in order to call it correctly appears missing.

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 coverage is 100% and the enum labels are already fully documented, so the schema does the heavy lifting. The description restates product/target market/current metrics at a high level and notes the sector-vs-benchmark distinction only implicitly, adding little beyond what the structured fields already say; baseline 3 applies.

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 verb and outcome — 'decide whether you have product market fit and whether to scale' — names the inputs consumed (product, target market, current metrics) and the artifact returned (a scorecard scoring each dimension against example benchmark ranges). It is distinguishable from siblings without opening any schema.

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

Usage Guidelines5/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 scale_paid_check when you need a broad PMF assessment against the tool's example benchmarks.' The alternative and the selecting condition are both stated, so the agent does not have to infer routing.

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