Skip to main content
Glama

Stratalize Intelligence

Get Saas Metrics Benchmark

get_saas_metrics_benchmark
Read-only

Use when assessing SaaS company financial health, preparing investor reporting, or benchmarking KPIs before a fundraise or board presentation. Returns Rule of 40, burn multiple, CAC payback, NRR, gross margin, and ARR growth targets by ARR band. Example: $10-50M ARR benchmark — Rule of 40 median 28, NRR median 108%, CAC payback 18 months — companies below median Rule of 40 face 2-3x valuation compression in current market. Source: Stratalize SaaS benchmark tables. $0.02 USDC per call.

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_usd": "<arr_usd>"
    },
    "name": "get_saas_metrics_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
arr_usdYesAnnual Recurring Revenue in USD
burn_multipleNoNet burn divided by net new ARR
growth_rate_pctNoYoY ARR growth %

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and non-destructive, so the safety profile is covered. The description adds information the annotations cannot: a per-call cost of $0.02 USDC and the data source (Stratalize benchmark tables), both of which affect whether an agent should invoke it. It still does not describe the response structure beyond the metric list.

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 when-to-use clause, then the return payload, then an example, source, and price. Every sentence carries information, though the illustrative valuation-compression sentence is the least essential and makes the definition slightly dense for a single fetch call.

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 no output schema, the description properly takes on the burden of describing return values and does so concretely, including sample median figures. The remaining gap is that the roles of the two optional parameters (burn_multiple, growth_rate_pct) are never explained, so an agent cannot tell whether passing them changes the output.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3 and the schema already documents all three parameters. The description adds real meaning by explaining that benchmarks are segmented 'by ARR band', which tells the agent what arr_usd actually selects, plus a worked example showing the values that come back for the $10-50M band.

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 (returns benchmarks) and enumerates the exact metrics returned: Rule of 40, burn multiple, CAC payback, NRR, gross margin, ARR growth, all keyed by ARR band. This clearly separates it from single-metric siblings like get_cac_benchmark, which it supersedes as a bundled SaaS finance scorecard.

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?

Gives concrete triggering situations: assessing SaaS financial health, investor reporting, benchmarking before a fundraise or board presentation. It does not name an alternative tool or state when not to use it, but the use-case framing is specific enough that an agent can route confidently.

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