Skip to main content
Glama

Senaro Personal Finance

PMI Removal Analysis

analyze_pmi_removal
Read-onlyIdempotent

Calculation, not advice. Verify with a professional before acting. Compute every standard PMI-removal pathway (HPA automatic at 78% LTV, HPA borrower-requested at 80% LTV, optional re-appraisal at a simplified 75% of current market value; the actual Fannie Mae ceiling is seasoning- and property-type-dependent, 75% for a one-unit home seasoned two to five years, 80% for five-plus, and 70% for investment and two- to four-unit properties), current monthly PMI cost, total PMI dollars between now and automatic removal, and the effective annual return of paying the gap-to-80% (of the original value) as a lump sum today. Supplying original_loan_term_months and loan_age_months also applies the 12 U.S.C. 4902(c) statutory final-termination midpoint, which bounds automatic removal at the earlier of the 78% schedule and that midpoint where HPA applies and the borrower is current. Pairs with compare_mortgage_terms for the broader refinance / pay-extra / drop-PMI decision.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolArgumentsYesJSON object with these parameters: current_balance: decimal > 0 (REQUIRED). Today's loan balance. original_purchase_price: decimal > 0 (REQUIRED). What you paid for the home (the purchase-price side of the HPA basis; when a closing appraisal is lower, see original_appraised_value). current_home_value: decimal > 0 (optional). When provided AND greater than the HPA original value (the lesser of purchase price and any closing appraisal), the response also computes the re-appraisal pathway (some lenders allow PMI removal based on current market value with a fresh appraisal). original_appraised_value: decimal > 0 (optional). The home's appraised value at closing. HPA sets the PMI trigger basis to the LESSER of purchase price and this appraisal (12 U.S.C. 4901); provide it when your closing appraisal came in below the purchase price. annual_pmi_rate_pct: decimal 0-5 (optional, default 0.5). Annual PMI as a percentage of the current loan balance. Typical conventional-loan PMI ranges from 0.3% to 1.5%. annual_rate_pct: decimal 0-20 (REQUIRED). Mortgage APR. monthly_payment: decimal > 0 (REQUIRED). Current P&I monthly payment (excluding tax/insurance/PMI). extra_monthly_payment: decimal >= 0 (optional, default 0). Extra principal each month beyond the regular payment. original_loan_term_months: integer 1-480 (optional). The loan's original term in months. Supplied together with loan_age_months, this computes the 12 U.S.C. 4902(c) statutory final-termination midpoint (12 U.S.C. 4901(7)) and bounds automatic_removal at the earlier of it and the 78% schedule date, where HPA applies and the borrower is current. Supplying either one without the other is rejected; both are required together. loan_age_months: integer 0-480 (optional). Months elapsed since origination. Cannot exceed original_loan_term_months when both are supplied. Supplying either one without the other is rejected; both are required together. See original_loan_term_months. Scope: conventional mortgages only. FHA loans use MIP (Mortgage Insurance Premium) with different rules. Typically MIP runs for the life of the loan when down payment < 10%. This tool does NOT model MIP. chart_title: string (optional) override for the chart title. Must not contain em-dashes or en-dashes. Max 120 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered. The description adds genuinely useful behavioral context beyond that: the 'calculation, not advice' disclaimer, the rule that supplying original_loan_term_months or loan_age_months alone is rejected, and that the statutory midpoint only bounds removal where HPA applies and the borrower is current.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The critical disclaimer is front-loaded, which is good, but the body is a single dense paragraph with heavily nested parentheticals (the Fannie Mae ceiling breakdown is buried mid-sentence). Every fact earns its place, yet the structure makes it harder to scan than it needs to be.

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?

For a complex financial calculation with no output schema, the description enumerates what the response computes and the conditions that unlock extra outputs (re-appraisal when current value exceeds the HPA basis; statutory midpoint when term and age are supplied). It is nearly self-sufficient, with only minor gaps in how results are presented.

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 documents every parameter including defaults, ranges, and the paired-parameter constraint. The description restates some of this (the term/age pairing and the statutory midpoint) but adds no syntax or format detail beyond the schema. Baseline 3 is appropriate.

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 – it computes PMI-removal pathways (HPA automatic at 78% LTV, borrower-requested at 80%, re-appraisal at 75%), monthly PMI cost, total PMI dollars, and effective return of paying the gap. It also names a sibling (compare_mortgage_terms) for the broader decision, so an agent can distinguish it without opening either schema.

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

Usage Guidelines4/5

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

Explicit scope exclusion: conventional mortgages only, FHA/MIP is not modeled and runs for life when down payment < 10%. It also routes the agent to compare_mortgage_terms for the broader refinance/pay-extra/drop-PMI decision. No explicit when-not-to-use for the PMI pathways themselves, but context is clear.

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