Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_subrogation_lien_reduction

Calculate reduced health insurance and ERISA subrogation lien payouts under Common Fund and Made-Whole doctrines using attorney fee percentages and pro-rata litigation costs.

Instructions

Health Insurance Subrogation Lien Reduction (Common Fund Doctrine) Calculator. Calculate mandatory legal reductions to health insurance and ERISA subrogation liens under the Common Fund Doctrine and Made-Whole Doctrine. Discipline: LEGAL. Governing mathematical model / formula: Net Lien = Gross Lien - (Gross Lien × Attorney Fee %) - Pro-Rata Litigation Costs.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of reduced_lien_payout_usd (Final Compromised Lien Payoff), total_lien_reduction_usd (Total Dollar Reduction Captured), attorney_fee_deduction (Common Fund Attorney Fee Share), pro_rata_expense_share (Pro-Rata Expense Share) using gross_medical_lien_usd (Asserted Health Insurance Lien ($ USD)), gross_tort_settlement_usd (Total Gross Tort Settlement ($)), attorney_contingency_fee_pct (Attorney Fee Percentage (%) in %), case_litigation_expenses_usd (Total Case Expenses ($)). 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 'Health Insurance Subrogation Lien Reduction (Common Fund Doctrine) 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): "subrogation-lien-reduction"

    • category (string): "legal"

    • name (string): "Health Insurance Subrogation Lien Reduction (Common Fund Doctrine) Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.reduced_lien_payout_usd (Final Compromised Lien Payoff): Formatted display string (e.g. '$19,894.00')

      • metrics.total_lien_reduction_usd (Total Dollar Reduction Captured): Formatted display string (e.g. '$12,106.00 (37.8% Cut)')

      • metrics.attorney_fee_deduction (Common Fund Attorney Fee Share): Formatted display string (e.g. '$10,666.00 Subtracted')

      • metrics.pro_rata_expense_share (Pro-Rata Expense Share): Formatted display string (e.g. '$1,440.00 Subtracted')

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

Input Schema

NameRequiredDescriptionDefault
gross_medical_lien_usdNoAsserted Health Insurance Lien ($ USD). Original subrogation lien claimed by Blue Cross, United, Aetna. Default: 32000. Min: 1000. Max: 500000.
gross_tort_settlement_usdNoTotal Gross Tort Settlement ($). Total personal injury recovery. Default: 100000. Min: 5000. Max: 2000000.
attorney_contingency_fee_pctNoAttorney Fee Percentage (%) (%). Contractual attorney fee percentage. Default: 33.33. Min: 25. Max: 45.
case_litigation_expenses_usdNoTotal Case Expenses ($). Costs advanced by law firm. Default: 4500. Min: 0. Max: 50000.

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 provided, the description carries the full behavioral burden and does so clearly: pure deterministic computation, machine floating-point precision, read-only, idempotent, stateless, zero side effects, and safe diagnostic errors for out-of-bounds inputs. This gives an agent enough confidence to invoke the tool without worrying about mutations or runtime exceptions.

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?

The description is front-loaded with purpose and formula, then organized into usage, behavior, and returns. It is somewhat verbose and repeats the tool name and parameter names already covered by the schema, but the structure remains clear and every major section serves a purpose.

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?

Given that no output schema exists, the description thoroughly documents the structured JSON return object, including status, calculator, category, formula, echoed inputs, computed metrics, and execution time. Combined with the behavior and validation notes, it is complete for a deterministic four-parameter calculator.

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 four parameters are already fully documented in the input schema. The description reiterates parameter names and meanings and adds the governing formula linking them to outputs, but it does not meaningfully expand parameter-level semantics beyond the schema baseline.

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 states a specific calculation: mandatory legal reductions to health insurance and ERISA subrogation liens under the Common Fund and Made-Whole doctrines. It names the governing formula and distinguishes the tool from the generic omni_universal_query dispatcher.

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?

It provides explicit WHEN TO USE and WHEN NOT TO USE sections, including the requirement for valid numerical inputs, and names sibling routing alternatives for generic dispatch. The guidance leaves little ambiguity about when this calculator should be selected.

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