Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_saas_rule_of_40

Calculates a SaaS Rule of 40 score by combining YoY revenue growth and FCF margin, then returns benchmark status, valuation premium, and growth profile.

Instructions

SaaS Rule of 40 Calculator. Calculate the Rule of 40 score balancing YoY ARR revenue growth rate percentage and Free Cash Flow (FCF) margin percentage. Discipline: FINANCE. Governing mathematical model / formula: Rule of 40 Score = YoY Revenue Growth Rate (%) + Profit Margin (%).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of rule_of_40_score (Rule of 40 Score), benchmark_status (Venture Benchmark Status), valuation_premium (Expected Public Multiple Premium), growth_profile (Operating Strategy Profile) using growth_rate_pct (Year-over-Year (YoY) Growth Rate in %), profit_margin_pct (Profitability (FCF or EBITDA Margin) in %). Guarantees exact machine floating-point precision, eliminating LLM arithmetic mistakes and formula hallucinations.

  • WHEN NOT TO USE: Do not use for qualitative evaluations or unquantified reasoning. All input parameters must be valid numerical values.

DISAMBIGUATION & BOUNDARIES:

  • Use this dedicated specialist tool for 'SaaS Rule of 40 Calculator' rather than generic dispatchers like omni_universal_query.

  • For multi-calculation chained jobs, use 'omni_batch_calculate'.

  • To inspect schema fields, see 'omni_describe_solver'.

BEHAVIOR & SAFETY:

  • Pure deterministic computation with machine floating-point precision.

  • Read-only, idempotent, and stateless. Zero side effects or persistent state mutations.

  • Input validation: All arguments are validated against physical and domain bounds. Out-of-bounds inputs return a safe diagnostic error status without throwing runtime exceptions.

RETURNS:

  • Structured JSON object containing:

    • status (string): "success" on valid execution or "error" if validation fails

    • calculator (string): "saas-rule-of-40"

    • category (string): "finance"

    • name (string): "SaaS Rule of 40 Calculator"

    • formula (string): Governing mathematical formula string

    • inputs (object): Echoed input parameter dictionary with applied defaults

    • metrics (object): Dictionary of computed outputs:

      • metrics.rule_of_40_score (Rule of 40 Score): Formatted display string (e.g. '50.0%')

      • metrics.benchmark_status (Venture Benchmark Status): Formatted display string (e.g. 'Passes Rule of 40 (Top Quartile)')

      • metrics.valuation_premium (Expected Public Multiple Premium): Formatted display string (e.g. 'Premium EV/ARR Multiple (> 12×)')

      • metrics.growth_profile (Operating Strategy Profile): Formatted display string (e.g. 'Hypergrowth Scaling (Growth > 40%)')

    • execution_time_ms (number): Latency in milliseconds.

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": "omni_saas_rule_of_40"
  }
}

Input Schema

NameRequiredDescriptionDefault
growth_rate_pctNoYear-over-Year (YoY) Growth Rate (%). YoY ARR or GAAP revenue growth percentage. Default: 45. Min: -50. Max: 300.
profit_margin_pctNoProfitability (FCF or EBITDA Margin) (%). Free Cash Flow or EBITDA margin percentage. Default: 5. Min: -100. Max: 80.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations supplied, the description fully carries the behavioral burden: it declares the tool read-only, idempotent, stateless, and free of side effects, and explains that out-of-bounds inputs return a diagnostic error rather than throwing. It also discloses the determinism/precision guarantee, which is the main reason to prefer this tool over LLM arithmetic.

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 purpose and formula, then cleanly sectioned, so an agent can scan it quickly. It is longer than necessary and repeats the input parameter meanings in the USAGE GUIDELINES section after the schema already defines them, but the RETURNS block earns its space given no output schema exists.

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?

For a two-parameter deterministic calculator with no output schema and no annotations, the definition covers purpose, formula, inputs, error behavior, disambiguation, and a full breakdown of the returned JSON including each metric. Nothing material is missing for correct invocation.

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%, with defaults, min/max bounds, and units already documented per property, so the baseline is 3. The description restates that growth_rate_pct is YoY ARR/GAAP growth and profit_margin_pct is FCF or EBITDA margin, but adds no format, edge-case, or interpretation guidance beyond the schema.

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 resource ('SaaS Rule of 40 Calculator... Calculate the Rule of 40 score') and gives the governing formula explicitly (Growth Rate % + Profit Margin %). It also names the outputs produced, so an agent can tell precisely what this tool computes versus siblings such as omni_rule_of_72 or omni_saas_magic_number.

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?

Contains explicit WHEN TO USE, WHEN NOT TO USE, and DISAMBIGUATION sections that route the agent away from omni_universal_query toward omni_batch_calculate for chained jobs and omni_describe_solver for schema inspection. It also states the precondition that all inputs must be valid numerical values.

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

Deploy Server

Other Tools