Skip to main content
Glama

curatedapi

FHA mortgage insurance (MIP) calculator

calc_finance_fha_mip
Read-only

The upfront and annual mortgage insurance premium on an FHA loan, from HUD's current rate tables, and how long the annual premium is charged.

An FHA-insured mortgage carries two insurance premiums. The upfront premium is 1.75% of the base loan amount and is usually added to the loan. The annual premium depends on the loan term, the base loan amount and the loan-to-value ratio, and is charged monthly for 11 years or for the whole mortgage term. This calculator reads both from the tables in HUD Mortgagee Letter 2023-05, which apply to loans endorsed on or after 20 March 2023.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "base_loan_amount": "<base_loan_amount>",
      "property_value": "<property_value>",
      "term_years": "<term_years>"
    },
    "name": "calc_finance_fha_mip"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionsNoPrecision and rounding of the results (default: rounding=half_even, decimals=2).
term_yearsYesThe mortgage term in years. Allowed: >= 1 and <= 30.
property_valueYesThe value the loan-to-value ratio is measured against: the lower of the price and the appraised value. Allowed: > 0 and <= 1000000000000000. Unit: currency.
base_loan_amountYesThe loan before the upfront premium is added. Allowed: > 0 and <= 1000000000000000. Unit: currency.
finance_upfront_mipNoWhether the upfront premium is added to the loan instead of paid in cash.

Output Schema

NameRequiredDescriptionDefault
inputsYesThe inputs as understood.
resultYes
formulaNo
receiptNoOnly with ?receipt=true: a signed receipt for this answer, a JSON Web Token signed with Ed25519 (alg EdDSA). Its claims are iss, iat, jti (the request id), endpoint, date and response (this response without the receipt). Check it with the keys at /.well-known/jwks.json or POST /v1/receipts/verify.
warningsYes
exactnessYesFor each decimal output: exact; rounded (correctly, to the precision); rounded_uncertified (the last digit could not be proven); or underflow (below 1e-100, reported as 0).
precisionNoThe precision and rounding that were applied.
calculatorYesThe calculator and version that ran.
referencesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), so the bar is lower, and the description still adds real domain behavior: the 1.75% upfront rate, that it is typically financed, that annual MIP depends on term/loan amount/LTV and runs 11 years or the full term, and the effective-date cutoff of the rate table. It does not address what happens outside the supported input ranges (term < 1, LTV extremes).

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?

Three tight sentences with the output and its two components front-loaded, followed by the rate-table provenance. The opening sentence is a verbless fragment, which slightly delays the actionable statement, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value explanation is unnecessary, and the description supplies the pricing rules, the premium-duration rule, and the regulatory vintage needed to trust the numbers. A five-parameter tool with nested options is left slightly under-covered on how rounding options interact with results.

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 schema already explains base_loan_amount as 'the loan before the upfront premium is added' and property_value as the LTV denominator. The description reinforces the drivers of the annual premium (term, loan amount, LTV) but adds no formatting, unit, or boundary detail beyond what the schema states, so 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?

Names the exact quantity computed (upfront and annual MIP on an FHA loan, plus duration of the annual premium) and pins the source to HUD Mortgagee Letter 2023-05. The FHA/MIP framing inherently separates it from the VA funding fee, USDA guarantee fee and generic mortgage siblings, though it never names any of them explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the domain: an agent can infer it applies to FHA-insured loans endorsed on or after 20 March 2023. There is no explicit 'use this instead of X when...' routing to calc_finance_mortgage or calc_finance_va_funding_fee, and no stated exclusions (e.g. pre-2023 endorsements, LTV above 95%).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources