Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_mortgage_solver

Calculates monthly principal and interest payments, total interest, total loan cost, and accelerated payoff savings for fixed-rate residential mortgages.

Instructions

Fixed-Rate Mortgage Payment & Amortization Calculator: Calculates exact monthly principal and interest (P&I) installments, total cumulative interest, total cost of loan, and accelerated payoff interest savings with extra monthly principal payments for fixed-rate residential mortgages.

GOVERNING MATHEMATICAL EQUATIONS:

  • Monthly Payment: M = P · [r(1+r)ⁿ] / [(1+r)ⁿ - 1], where r = APR / 1200 and n = years × 12.

  • Total Cumulative Interest = (M · n) - P

  • Total Cost of Loan = M · n

  • Accelerated Payoff: Extra monthly principal directly reduces remaining balance, reducing subsequent monthly interest accrual.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for calculating monthly mortgage payments, interest burden, and early payoff schedules for residential fixed-rate home loans.

  • WHEN NOT TO USE: Do not use for commercial construction loans, interest-only balloon mortgages, or reverse mortgages.

  • SIBLING DIFFERENTIATION: Dedicated strictly to residential fixed-rate amortizing first mortgages. For short-term real estate investment bridge loans or flip financing, query slug 'hard-money-loan' or 'hard-money-points' via 'omni_universal_query'. For revolving home equity lines of credit, query slug 'heloc' via 'omni_universal_query'. For comparing multiple loan options (e.g. 15-year vs 30-year), use 'omni_batch_calculate'.

PARAMETER RELATIONSHIPS & CONSTRAINTS:

  • 'loan_amount': Total borrowed principal balance in USD ($) (min 1,000, max 20,000,000, default 400,000).

  • 'interest_rate_pct': Fixed annual interest rate percentage (APR) (min 0.1, max 25.0, default 6.75). Converted internally to monthly rate r = rate / 1200.

  • 'loan_term_years': Loan term duration in years (min 1, max 50, default 30). Total payments n = years × 12.

  • 'extra_monthly_payment': Optional additional principal paid each month in USD ($) (min 0, default 0). Directly accelerates amortization schedule.

BEHAVIOR, SAFETY & DETERMINISM:

  • Pure deterministic loan amortization calculation with IEEE 754 precision.

  • Read-only, idempotent, and stateless. Zero side effects or persistent mutations.

RETURN VALUE SCHEMA & QUANTITIES:

  • source (string): Canonical documentation URL (https://omnioperand.com/finance/mortgage/)

  • inputs (object): Echoed input parameter values

  • metrics (object): Calculated financial metrics:

    • monthly_payment (number): Base monthly principal and interest installment ($/mo)

    • total_monthly_payment (number): Total monthly payment including extra principal ($/mo)

    • total_interest_paid (number): Total cumulative interest paid over the life of the loan ($)

    • total_cost_of_loan (number): Total cumulative principal plus interest ($)

    • payoff_months (number): Total number of months required to reach zero balance

    • payoff_years (number): Equivalent payoff timeline in years

    • interest_saved_with_extra (number): Total interest saved due to extra principal payments ($)

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_mortgage_solver"
  }
}

Input Schema

NameRequiredDescriptionDefault
loan_amountNoTotal borrowed mortgage principal amount in USD ($).
loan_term_yearsNoMortgage amortization duration in years (typically 15, 20, or 30 years).
interest_rate_pctNoAnnual percentage rate (APR) as a whole number (e.g. 6.75 for 6.75%).
extra_monthly_paymentNoOptional extra principal payment added to each monthly installment in USD ($).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

A4.4/5.0
Behavior4/5

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

With annotations empty, the description carries the full burden and does so: pure deterministic calculation, IEEE 754 precision, read-only, idempotent, stateless, zero side effects. It does not spell out edge-case behavior (e.g., what happens if extra_monthly_payment exceeds the base installment or payoff is reached early), which is the one behavioral gap for a numeric solver.

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 — purpose first, then equations, usage, parameters, behavior, and returns, with clear headers and no buried conclusion. It is verbose for a 4-parameter calculator, and the min/max/default listing duplicates the schema verbatim rather than earning its space.

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?

No output schema exists, but the description fully enumerates every returned metric (monthly_payment, total_interest_paid, payoff_months, interest_saved_with_extra, etc.) plus a source URL, so an agent knows exactly what it gets back. Input constraints, formulas, and scope are all covered for a tool of this complexity.

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 coverage is 100%, so ranges, defaults, and descriptions already exist in structured form and the parameter section largely restates them. The added value is modest but real: the internal conversion r = rate / 1200 and the note that extra principal 'directly accelerates amortization' explain how inputs feed the formula.

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 exact monthly principal and interest installments, total cumulative interest, total cost of loan, and accelerated payoff interest savings') scoped to fixed-rate residential mortgages. It explicitly names the loan products it does not cover and routes to named siblings.

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?

Contains explicit WHEN TO USE and WHEN NOT TO USE sections with concrete exclusions (commercial construction, interest-only balloon, reverse mortgages). SIBLING DIFFERENTIATION names the exact alternatives and the slugs to query for bridge loans, HELOCs, and multi-scenario comparison via omni_batch_calculate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.