Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_structured_settlement_npv

Calculates the fair lump-sum present value and discount haircut for selling structured settlement annuity payments, helping assess a buyout offer against judicial fairness benchmarks.

Instructions

Structured Settlement Annuity Lump-Sum Present Value (NPV). Calculate fair market cash lump-sum present value (NPV) and purchasing company discount factoring haircut when selling structured settlement annuity payments. Discipline: LEGAL. Governing mathematical model / formula: NPV = Σ [Monthly Payment / (1 + r / 12)ᵗ] | Discount Rate r typically 8% - 15%.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of lump_sum_cash_offer (Fair Net Lump-Sum Cash Offer), total_nominal_payments (Total Future Guaranteed Payments), effective_discount_haircut (Discount Haircut Surrendered), fair_court_benchmark (Judicial Approval Fairness Assessment) using monthly_annuity_payment (Monthly Annuity Payment ($)), remaining_payment_years (Remaining Payment Duration (Years) in yrs), purchaser_discount_rate_pct (Factoring Company Discount Rate (%) 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.

  • SIBLING ROUTING: Use this dedicated specialist tool for 'Structured Settlement Annuity Lump-Sum Present Value (NPV)' 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): "structured-settlement-npv"

    • category (string): "legal"

    • name (string): "Structured Settlement Annuity Lump-Sum Present Value (NPV)"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.lump_sum_cash_offer (Fair Net Lump-Sum Cash Offer): Formatted display string (e.g. '$149,420.00')

      • metrics.total_nominal_payments (Total Future Guaranteed Payments): Formatted display string (e.g. '$315,000.00')

      • metrics.effective_discount_haircut (Discount Haircut Surrendered): Formatted display string (e.g. '52.6% Lost to Discounting ($165,580)')

      • metrics.fair_court_benchmark (Judicial Approval Fairness Assessment): Formatted display string (e.g. 'Reasonable Rate for Structured Buyout')

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

Input Schema

NameRequiredDescriptionDefault
monthly_annuity_paymentNoMonthly Annuity Payment ($). Guaranteed tax-free structured settlement payment. Default: 1750. Min: 100. Max: 25000.
remaining_payment_yearsNoRemaining Payment Duration (Years) (yrs). Years of guaranteed annuity payments remaining. Default: 15. Min: 1. Max: 40.
purchaser_discount_rate_pctNoFactoring Company Discount Rate (%) (%). Annual discount rate quoted by settlement buyer (typically 9% - 14%). Default: 11.5. Min: 4. Max: 25.

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?

With no annotations supplied, the description carries the full burden and does so well: it declares the tool read-only, idempotent, stateless, side-effect free, and specifies that out-of-bounds inputs return a diagnostic error status rather than throwing. It stops short of stating precision/rounding guarantees for the outputs or whether the formula uses a monthly-compounding assumption beyond the formula string itself, so it is not quite exhaustive.

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 a one-line purpose, then clearly sectioned usage, behavior, and returns. Some material is redundant (the tool name, category, and discipline are restated in multiple places), but the length is justified by the absence of an output schema.

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 3-parameter, zero-required, computation-only tool with no output schema and no annotations, the definition covers inputs, validation bounds behavior, formula, and the full shape of the returned JSON metrics. An agent has everything needed to call it and interpret the result 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 defaults, min/max, and units are already documented, making 3 the baseline. The description repeats the parameter meanings (monthly payment, remaining years, discount rate) without adding new semantics, and it mildly conflicts with itself on typical rates (8%-15% in the formula line vs. 9%-14% in the schema), which slightly reduces confidence rather than adding clarity.

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: calculates the lump-sum present value (NPV) and discount haircut for selling structured settlement annuity payments, and even names the governing formula. This is clearly distinguishable from the generic omni_universal_query dispatcher it references.

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 computation of four named outputs from three named inputs), WHEN NOT TO USE (qualitative/unquantified reasoning, non-numeric inputs), and SIBLING ROUTING (prefer this specialist over omni_universal_query). No inference is required to pick this tool over alternatives.

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