Skip to main content
Glama

Mode VC Chart: AI Adoption Rate Among US Businesses

SaaS Metrics Calculator (Rule of 40, NRR, GRR, Magic Number, CAC Payback)

calc_saas_metrics
Read-onlyIdempotent

Computes Rule of 40, net and gross revenue retention, SaaS magic number, CAC payback and spend per new customer from the numbers you give, with the public benchmark each is judged against. Leave a group of inputs out to get n/a for the metrics that need it. Same math as https://modevc.com/tools/saas-metrics-calculator.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "calc_saas_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
arr_nowNoARR now in USD.
new_mrrNoNew MRR added in USD. For CAC payback.
margin_pctNoProfit margin in percent for the Rule of 40. Can be negative.
margin_kindNoWhich margin margin_pct is. Web default FCF margin.
cohort_churnNoChurned ARR from that group in USD.
new_customersNoNew customers won. For spend per new customer.
cohort_expansionNoExpansion ARR from that group in USD.
cohort_start_arrNoStarting ARR of one customer group 12 months ago, in USD. Needed for NRR and GRR.
gross_margin_pctNoGross margin in percent. For CAC payback.
arr_12_months_agoNoARR 12 months ago in USD. Needed for growth and Rule of 40.
cohort_contractionNoContraction (downgrades) ARR from that group in USD.
revenue_last_quarterNoRevenue in the last quarter in USD. For the magic number.
revenue_prior_quarterNoRevenue in the prior quarter in USD.
sales_marketing_spendNoSales and marketing spend in USD. Prior quarter for the magic number; the same figure drives CAC payback and spend per customer, as on the web calculator.

Output Schema

NameRequiredDescriptionDefault
as_ofNo
provenanceYes
source_urlsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "as_of": {
      +      "type": "string"
      +    },
      +    "provenance": {
      +      "properties": {
      +        "as_of": {
      +          "type": "string"
      +        },
      +        "as_of_basis": {
      +          "type": "string"
      +        },
      +        "sources": {
      +          "items": {
      +            "type": "object"
      +          },
      +          "type": "array"
      +        }
      +      },
      +      "required": [
      +        "as_of",
      +        "as_of_basis",
      +        "sources"
      +      ],
      +      "type": "object"
      +    },
      +    "source_urls": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "provenance"
      +  ],
      +  "type": "object"
      +}
  2. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so safety is covered. The description adds two useful behavioral facts beyond that: incomplete input groups yield 'n/a' rather than an error, and results include the public benchmark each metric is judged against, plus parity with the Mode VC web calculator. It stops short of stating units handling, rounding, or error behavior for contradictory inputs.

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 verb and metric list, then two short sentences for the partial-input rule and source parity. No filler. The first sentence is long but each clause enumerates a distinct output, so it earns its length.

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?

For a 14-parameter, zero-required calculator with an output schema and full annotations, the description covers purpose, partial-input semantics, and result content (benchmark comparison). What remains unstated — rounding, unit validation, how a negative margin_pct is handled — is minor given the schema notes and the output schema.

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 every parameter carries its own unit and purpose note, so the schema does the heavy lifting. The description only adds the framing that inputs cluster into groups and that the same sales_marketing_spend figure drives three metrics. Baseline 3 is correct here.

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?

Names a specific verb (computes) and enumerates the exact metric set: Rule of 40, NRR, GRR, magic number, CAC payback, spend per new customer. This is enough for an agent to distinguish it from the other calc_* siblings (burn multiple, SAFE dilution, etc.) without opening the 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?

The sentence 'Leave a group of inputs out to get n/a for the metrics that need it' is real usage guidance: it tells the agent that partial invocation is valid and what the fallback result looks like. It does not name exclusions or alternatives, but the metric list itself makes the boundary obvious against sibling calculators.

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.

Resources