Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_breach_of_contract_damages

Calculate expectation damages, incidental losses, consequential lost profits, and mitigation offsets in commercial breach-of-contract disputes with deterministic arithmetic.

Instructions

Breach of Contract Expectation & Consequential Damages Calculator. Calculate expectation damages, incidental losses, consequential lost profits (Hadley v. Baxendale rule), and mitigation offsets in commercial contract disputes. Discipline: LEGAL. Governing mathematical model / formula: Expectation Damages = (Contract Price - Mitigation Revenue) + Incidental Expenses + Consequential Damages.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of total_recoverable_damages (Total Recoverable Breach Damages), direct_expectation_loss (Direct Expectation Loss), mitigation_credit_offset (Mitigation Credit Subtracted), incidental_consequential_total (Secondary Losses Recovered) using agreed_contract_price_usd (Full Agreed Contract Value ($ USD)), mitigation_resale_revenue (Mitigation Substitute Revenue ($)), incidental_expenses_usd (Incidental Storage & Brokering Costs ($)), consequential_lost_profits_usd (Foreseeable Consequential Damages ($)). 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 'Breach of Contract Expectation & Consequential Damages 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): "breach-of-contract-damages"

    • category (string): "legal"

    • name (string): "Breach of Contract Expectation & Consequential Damages Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.total_recoverable_damages (Total Recoverable Breach Damages): Formatted display string (e.g. '$112,500.00')

      • metrics.direct_expectation_loss (Direct Expectation Loss): Formatted display string (e.g. '$80,000.00')

      • metrics.mitigation_credit_offset (Mitigation Credit Subtracted): Formatted display string (e.g. '$95,000.00 Offset')

      • metrics.incidental_consequential_total (Secondary Losses Recovered): Formatted display string (e.g. '$32,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_breach_of_contract_damages"
  }
}

Input Schema

NameRequiredDescriptionDefault
incidental_expenses_usdNoIncidental Storage & Brokering Costs ($). Storage, return freight, and re-listing expenses. Default: 8500. Min: 0. Max: 100000.
agreed_contract_price_usdNoFull Agreed Contract Value ($ USD). Original promised contract consideration. Default: 175000. Min: 1000. Max: 10000000.
mitigation_resale_revenueNoMitigation Substitute Revenue ($). Money recovered by selling goods/services to an alternate buyer. Default: 95000. Min: 0. Max: 10000000.
consequential_lost_profits_usdNoForeseeable Consequential Damages ($). Downstream lost profits reasonably foreseeable at contract signing. Default: 24000. Min: 0. Max: 1000000.

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 carries the whole burden and does so: it declares pure deterministic computation, read-only, idempotent, stateless, zero side effects, and that out-of-bounds inputs return a safe diagnostic error rather than throwing. It also spells out the full return envelope (status, calculator, metrics, execution_time_ms).

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?

Well front-loaded with the formula and structured into WHEN TO USE, boundaries, safety, and returns sections. It is somewhat padded, repeating each parameter name alongside a human label that the schema already provides, but no section is wasted.

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?

There is no output schema, and the description compensates by fully enumerating the response fields and the computed metric strings. For a four-parameter legal calculator this leaves an agent with nothing essential missing in order 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%, so the schema already documents every parameter's meaning, units, defaults, and bounds. The description restates the four inputs with their human labels but adds no new semantics such as edge-case behavior or interaction between mitigation revenue and expectation loss. Baseline 3 applies.

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 expectation damages, incidental losses, consequential lost profits... and mitigation offsets'), names the governing formula, and names the four computed outputs. It is clearly distinguishable from generic dispatchers and from other damage-domain siblings by the Hadley v. Baxendale framing.

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 (deterministic calculation of the four named metrics), WHEN NOT TO USE (qualitative or unquantified reasoning, non-numeric inputs), and disambiguation against named alternatives including omni_universal_query, omni_batch_calculate, and omni_describe_solver.

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