Skip to main content
Glama

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. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, open-world), so the bar is lower; the description still adds real context the annotations lack — the underlying data source (Stratalize SaaS benchmark tables) and an explicit price of $0.02 USDC per call. It also gives interpretive context (below-median Rule of 40 correlates with 2-3x valuation compression) that helps the agent frame results, though it says nothing about caching or rate limits.

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?

It is front-loaded with a 'Use when...' clause, then return values, then an illustrative example, source, and price — a sensible order. The worked example and the valuation-compression aside are somewhat verbose, but each conveys usable calibration information rather than filler.

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 three parameters, one required, no output schema, and no nested objects, the description does the work the absent output schema would otherwise do by enumerating returned metrics. The remaining gap is that it never explains how supplying burn_multiple or growth_rate_pct changes the response, which an agent might reasonably want before passing them.

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 each parameter is already documented in the schema; the description only adds the notion that outputs are segmented 'by ARR band', which motivates arr_usd as required. The optional burn_multiple and growth_rate_pct inputs are never mentioned, so no meaning is added for two of the three parameters.

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?

The description names a specific resource and verb — it 'Returns Rule of 40, burn multiple, CAC payback, NRR, gross margin, and ARR growth targets by ARR band' — so the agent knows exactly what comes back. The multi-metric, ARR-banded scope also implicitly separates it from the single-metric siblings (e.g. get_cac_benchmark).

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?

It states clear triggering contexts: assessing SaaS financial health, investor reporting, benchmarking before a fundraise or board presentation. It does not name a when-not condition or point to an alternative sibling, so it stops short of full 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