Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_burn_multiple

Calculates the Bessemer Burn Multiple by dividing net cash burn by net new ARR, returning capital efficiency tier, cost per ARR dollar, and growth verdict.

Instructions

Bessemer Burn Multiple Calculator. Calculate the Bessemer Venture Partners Burn Multiple measuring net cash burned for each dollar of Net New ARR generated. Discipline: FINANCE. Governing mathematical model / formula: Burn Multiple = Net Burn / Net New ARR.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of burn_multiple_score (Burn Multiple), capital_efficiency_tier (Bessemer Capital Efficiency Tier), cost_per_arr_dollar (Cash Burned per $1.00 ARR Added), growth_verdict (Investor Perspective) using net_burn_amount (Annual / Period Net Cash Burn), net_new_arr_added (Net New ARR Generated). 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.

  • SIBLING ROUTING: Use this dedicated specialist tool for 'Bessemer Burn Multiple Calculator' rather than generic dispatchers like omni_universal_query. For cross-discipline dynamic dispatch, see omni_universal_query.

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): "burn-multiple"

    • category (string): "finance"

    • name (string): "Bessemer Burn Multiple Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.burn_multiple_score (Burn Multiple): Formatted display string (e.g. '1.20×')

      • metrics.capital_efficiency_tier (Bessemer Capital Efficiency Tier): Formatted display string (e.g. 'Good (1.0x - 1.5x)')

      • metrics.cost_per_arr_dollar (Cash Burned per $1.00 ARR Added): Formatted display string (e.g. '$1.20')

      • metrics.growth_verdict (Investor Perspective): Formatted display string (e.g. 'Fundable Series A/B Growth Profile')

    • 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_burn_multiple"
  }
}

Input Schema

NameRequiredDescriptionDefault
net_burn_amountNoAnnual / Period Net Cash Burn. Total cash burned in measurement period. Default: 2400000. Min: 10000. Max: 100000000.
net_new_arr_addedNoNet New ARR Generated. Net ARR added in same measurement period. Default: 2000000. Min: 10000. Max: 100000000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4/5.0
Behavior3/5

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

With no annotations supplied, the description does carry the safety burden and does so well: read-only, idempotent, stateless, no side effects, bounded input validation, and errors returned as a status rather than thrown exceptions. However, it never explains the actual Burn Multiple interpretation boundaries (what tier thresholds map to which verdict), so the agent cannot sanity-check a result; the disclosure is thorough on plumbing but thin on domain behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

It is well-structured and front-loaded with purpose before usage and behavior, but it is substantially over-written: the floating-point-precision guarantee is asserted twice, the RETURNS block re-explains metrics that duplicate the same ratio four ways, and section headers inflate length for a two-parameter pure function.

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 and no annotations, the description must cover purpose, routing, safety, and return shape, and it covers all four including the full response field list. The remaining gap is domain semantics – the tier thresholds and formatting rules behind the returned display strings are never stated.

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 both properties already document defaults and min/max bounds, so the baseline applies. The description restates the same parameter definitions (net_burn_amount as annual/period net cash burn, net_new_arr_added) without adding period-matching rules or units beyond what the schema gives.

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 ("Calculate the Bessemer Venture Partners Burn Multiple") and gives the governing formula, Burn Multiple = Net Burn / Net New ARR. It also names the outputs the calculation produces, so the agent can tell exactly what this returns versus siblings like omni_runway_burn.

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?

Provides explicit WHEN TO USE with the enumerated outputs and inputs, an explicit WHEN NOT TO USE clause (qualitative reasoning, non-numeric inputs), and sibling routing that names omni_universal_query as the generic alternative and defers cross-discipline dispatch to it. Nothing about selection is left to inference.

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