Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_business_interruption_insurance

Calculates business interruption insurance loss recovery from projected revenue, avoided COGS, continuing fixed costs, and mitigation expenses, returning covered claim and lost profit.

Instructions

Business Interruption Loss & Gross Earnings Formula Calculator. Calculate business interruption insurance loss recovery, net profit reduction, continuing payroll overhead, and extra expense reimbursement. Discipline: LEGAL. Governing mathematical model / formula: Business Interruption Loss = Net Profit That Would Have Been Earned + Continuing Normal Operating Expenses.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of total_covered_claim_amount (Total Business Interruption Claim), lost_net_operating_profit (Lost Net Business Profit), continuing_expenses_covered (Continuing Fixed Costs Reimbursed), extra_expense_recovery (Extra Expense Allowance) using projected_gross_revenue_usd (Projected Lost Gross Revenue ($ USD)), normal_cost_of_goods_sold (Avoided Cost of Goods Sold (COGS $)), continuing_operating_expenses (Continuing Fixed Overhead ($)), extra_expenses_incurred (Extra Expenses to Mitigate Loss ($)). 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 'Business Interruption Loss & Gross Earnings Formula 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): "business-interruption-insurance"

    • category (string): "legal"

    • name (string): "Business Interruption Loss & Gross Earnings Formula Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.total_covered_claim_amount (Total Business Interruption Claim): Formatted display string (e.g. '$173,500.00')

      • metrics.lost_net_operating_profit (Lost Net Business Profit): Formatted display string (e.g. '$90,000.00')

      • metrics.continuing_expenses_covered (Continuing Fixed Costs Reimbursed): Formatted display string (e.g. '$65,000.00')

      • metrics.extra_expense_recovery (Extra Expense Allowance): Formatted display string (e.g. '$18,500.00')

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

Input Schema

NameRequiredDescriptionDefault
extra_expenses_incurredNoExtra Expenses to Mitigate Loss ($). Temporary facility rental, emergency equipment expedite fees. Default: 18500. Min: 0. Max: 500000.
normal_cost_of_goods_soldNoAvoided Cost of Goods Sold (COGS $). Raw materials and inventory purchases saved during closure. Default: 85000. Min: 0. Max: 5000000.
projected_gross_revenue_usdNoProjected Lost Gross Revenue ($ USD). Revenue business would have generated during shutdown period. Default: 240000. Min: 10000. Max: 10000000.
continuing_operating_expensesNoContinuing Fixed Overhead ($). Rent, key employee payroll, debt interest, utilities. Default: 65000. Min: 2500. Max: 2000000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden and it does so well: it declares the tool read-only, idempotent, stateless with zero side effects, and explains that out-of-bounds inputs return a safe diagnostic error rather than throwing. What is missing is any statement about formula assumptions or scope limits (e.g. whether period-of-indemnity or deductible logic is modeled), which matters for an insurance-loss calculator.

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?

Purpose and formula are front-loaded, and the long RETURNS block is justified because no output schema exists. It is somewhat verbose, restating constant fields like calculator name and category, but every major section carries usable information.

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?

With no annotations and no output schema, the definition compensates by describing the return JSON shape, status/error semantics, metric keys with example values, and validation behavior. Combined with the stated formula and input-to-output mapping, an agent has everything needed to call it correctly.

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 and min/max already documented on every parameter, so the schema does the heavy lifting and a baseline 3 applies. The description restates each parameter name with its label but adds no units, formatting rules, or interpretation guidance beyond what the schema already contains.

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 verb and resource ('Business Interruption Loss & Gross Earnings Formula Calculator') and enumerates the four computed outputs (total claim, lost net profit, continuing expenses, extra expense), so an agent knows exactly what it produces. It also explicitly contrasts itself with generic dispatchers, making it distinguishable from siblings without opening the schema.

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?

There are explicit WHEN TO USE and WHEN NOT TO USE sections, plus a disambiguation block routing chained jobs to omni_batch_calculate and schema inspection to omni_describe_solver. The exclusion for qualitative or non-numeric input is stated directly rather than 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