Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_refinance

Calculate mortgage refinance savings, new monthly payments, lifetime interest reduction, and closing-cost breakeven timeline to determine if refinancing pays off.

Instructions

Mortgage Refinance & Breakeven Calculator. Calculate monthly payment savings, lifetime interest reduction, and closing cost breakeven horizon when refinancing a home mortgage. Discipline: FINANCE. Governing mathematical model / formula: Breakeven Months = Total Closing Costs / (Current Payment - New Payment).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of monthly_savings (Monthly Payment Savings), breakeven_months (Breakeven Timeline), new_monthly_payment (New Monthly Payment (P&I)), lifetime_savings (Net Lifetime Savings) using balance (Remaining Balance), curr_rate (Current Interest Rate (%) in %), curr_term (Remaining Years in yrs), new_rate (New Refinance Rate (%) in %), new_term (New Loan Term (Years) in yrs), closing_costs (Total Closing Costs). 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 'Mortgage Refinance & Breakeven 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): "refinance"

    • category (string): "finance"

    • name (string): "Mortgage Refinance & Breakeven Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.monthly_savings (Monthly Payment Savings): Formatted display string (e.g. '$214.50')

      • metrics.breakeven_months (Breakeven Timeline): Formatted display string (e.g. '25.6 months')

      • metrics.new_monthly_payment (New Monthly Payment (P&I)): Formatted display string (e.g. '$2,042.80')

      • metrics.lifetime_savings (Net Lifetime Savings): Formatted display string (e.g. '$48,220.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_refinance"
  }
}

Input Schema

NameRequiredDescriptionDefault
balanceNoRemaining Balance. Current outstanding mortgage loan balance. Default: 350000. Min: 10000. Max: 2000000.
new_rateNoNew Refinance Rate (%) (%). Offered new interest rate. Default: 5.75. Min: 1. Max: 15.
new_termNoNew Loan Term (Years) (yrs). Term of the new replacement mortgage. Default: 30. Min: 10. Max: 30.
curr_rateNoCurrent Interest Rate (%) (%). Your current mortgage note rate. Default: 6.875. Min: 1. Max: 15.
curr_termNoRemaining Years (yrs). Number of years left on existing mortgage. Default: 27. Min: 1. Max: 30.
closing_costsNoTotal Closing Costs. Origination, appraisal, title, and lender fees. Default: 5500. Min: 0. Max: 25000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.4/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 full disclosure burden and does so: deterministic computation, machine floating-point precision, read-only/idempotent/stateless, zero side effects, and bounded-input validation that returns a diagnostic error status rather than throwing. That is the behavioral profile an agent needs before invoking.

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?

Header-based structure (USAGE GUIDELINES, BEHAVIOR & SAFETY, RETURNS) is scannable and front-loads purpose plus the governing formula. It is on the long side and repeats the calculator name and metric labels verbatim in several places, but the returns breakdown is justified because no output schema exists.

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?

The tool is a self-contained stateless calculator; the description supplies the formula, the full returns contract (status/calculator/category/formula/inputs/metrics with unit-bearing display formats), and failure semantics. With no output schema, the RETURNS block fills exactly the gap an agent would otherwise have.

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 six parameters, their units, defaults, and min/max bounds are fully documented in the schema. The description's parameter list (balance, curr_rate, curr_term, new_rate, new_term, closing_costs) largely restates the schema with no added semantics such as interplay or how the two rates combine — baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific domain verb+resource ('Mortgage Refinance & Breakeven Calculator') and enumerates the computed quantities (monthly savings, lifetime interest reduction, breakeven horizon). It distinguishes itself from the generic dispatcher omni_universal_query, but does not differentiate from nearer siblings such as omni_auto_refinance_savings, omni_student_loan_refinance, or omni_blended_mortgage_rate — the word 'mortgage' carries that load implicitly.

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?

Explicit WHEN TO USE, WHEN NOT TO USE, and SIBLING ROUTING sections tell the agent both the positive trigger (deterministic refinance math on balance/rates/terms/closing costs) and the exclusion (qualitative or unquantified reasoning), plus the routing alternative for generic or cross-discipline dispatch.

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