Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_fha_loan

Calculate FHA monthly mortgage payments, including principal and interest, monthly MIP, and financed upfront MIP, from purchase price, down payment percentage, and interest rate.

Instructions

FHA Loan & Mortgage Insurance (MIP) Calculator. Calculate monthly FHA payments including upfront (UFMIP) and annual monthly mortgage insurance premiums with minimum 3.5% down payment. Discipline: FINANCE. Governing mathematical model / formula: Total Financed Loan = Purchase Price - Down Payment + (Base Loan × 1.75% UFMIP).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of total_monthly (Total Monthly FHA Payment), base_payment (Base Principal & Interest), monthly_mip (Monthly FHA MIP (0.55%)), upfront_mip (Upfront MIP Financed (1.75%)) using purchase_price (Home Purchase Price), down_payment_pct (Down Payment (%) in %), interest_rate (Interest 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.

DISAMBIGUATION & BOUNDARIES:

  • Use this dedicated specialist tool for 'FHA Loan & Mortgage Insurance (MIP) 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): "fha-loan"

    • category (string): "finance"

    • name (string): "FHA Loan & Mortgage Insurance (MIP) Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.total_monthly (Total Monthly FHA Payment): Formatted display string (e.g. '$2,069.45')

      • metrics.base_payment (Base Principal & Interest): Formatted display string (e.g. '$1,927.85')

      • metrics.monthly_mip (Monthly FHA MIP (0.55%)): Formatted display string (e.g. '$141.60')

      • metrics.upfront_mip (Upfront MIP Financed (1.75%)): Formatted display string (e.g. '$5,404.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_fha_loan"
  }
}

Input Schema

NameRequiredDescriptionDefault
interest_rateNoInterest Rate (%) (%). 30-year fixed FHA note rate. Default: 6.25. Min: 2. Max: 12.
purchase_priceNoHome Purchase Price. Agreed home purchase price. Default: 320000. Min: 50000. Max: 1500000.
down_payment_pctNoDown Payment (%) (%). Minimum 3.5% down payment. Default: 3.5. Min: 3.5. Max: 20.

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 full burden and does: it declares the tool read-only, idempotent, stateless, deterministic, and specifies that out-of-bounds inputs return a safe diagnostic error rather than throwing — genuinely useful behavioral context for a calculator.

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-structured with labeled sections (usage, disambiguation, behavior, returns) and front-loaded purpose. Slightly padded by repeated formula text and echoed output metadata fields (calculator, category, name) that an agent does not need to act on.

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, so the RETURNS block appropriately enumerates status, inputs echo, and each computed metric with example formatting — exactly the information needed to consume results. Nothing required for correct invocation is missing.

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 each parameter's meaning, default, and min/max are already documented in the schema. The description restates the parameter names and units in the usage section but adds no new semantic detail 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?

First line names the exact resource (FHA Loan & Mortgage Insurance / MIP) and states the concrete computation: monthly FHA payment including UFMIP and annual MIP. The governing formula (Base Loan × 1.75% UFMIP) makes it unmistakable versus siblings like omni_va_loan or omni_hard_money_loan.

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 lists the four outputs and three inputs with units, and WHEN NOT TO USE excludes qualitative reasoning. Disambiguation section names concrete alternatives (omni_universal_query for generic dispatch, omni_batch_calculate for chained jobs, omni_describe_solver for schema inspection).

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