Skip to main content
Glama

Estimate a SaaS company's value

estimate_saas_valuation
Read-onlyIdempotent

Runs the Founder Ventures SaaS Valuation Calculator: a revenue multiple range from ARR, growth, net revenue retention, gross margin and profitability, based on the SaaS Capital formula and the current public SaaS multiple. An estimate, not an offer.

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": {
      "arr": "<arr>",
      "growth_pct": "<growth_pct>",
      "nrr_pct": "<nrr_pct>"
    },
    "name": "estimate_saas_valuation"
  }
}

Input Schema

NameRequiredDescriptionDefault
arrYesAnnual recurring revenue in USD.
fundingNo
nrr_pctYesNet revenue retention in %, for example 104.
growth_pctYesYear-over-year ARR growth in %, for example 30.
profitabilityNo
gross_margin_pctNoGross margin in %, default 80.

Output Schema

NameRequiredDescriptionDefault
urlYes
valueYes
multipleYes
warningsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the calculation follows the SaaS Capital formula and incorporates a live 'current public SaaS multiple', meaning results shift over time, plus an explicit accuracy disclaimer ('An estimate, not an offer'). Return shape is left to the 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.

Conciseness5/5

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

Two tight sentences: method and inputs first, disclaimer last. No filler, no restatement of the title, and the most important framing is front-loaded.

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?

With annotations covering safety and an output schema covering the return value, the description supplies the remaining essentials: methodology, input set, and the estimate caveat. It omits only minor points such as the effective date of the 'current' multiple and the unused-enum behavior, which are not blocking for a correct call.

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 67%, and the description echoes five of the six inputs while adding no format detail beyond what the schema already states (percent conventions, USD, defaults). The 'funding' parameter is never mentioned, and the description introduces an implied external input (the current public multiple) that the caller cannot set.

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 verb and resource ('Runs the Founder Ventures SaaS Valuation Calculator') and enumerates the actual drivers used (ARR, growth, NRR, gross margin, profitability). It never explicitly contrasts itself with adjacent siblings such as founder_exit_take_home, so it stops just short of full sibling differentiation.

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?

Usage is implied by the tool's nature: it is for producing a valuation estimate from SaaS metrics. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative such as founder_exit_take_home for exit proceeds. The closing 'An estimate, not an offer' is a caveat about the output rather than routing guidance.

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