Skip to main content
Glama

converters_mortgage

Read-onlyIdempotent

Mortgage calculator: payment with taxes, insurance, PMI and HOA, extra payments, biweekly and payoff date

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": {
      "homePrice": "<homePrice>",
      "ratePct": "<ratePct>",
      "years": "<years>"
    },
    "name": "converters_mortgage"
  }
}

Input Schema

NameRequiredDescriptionDefault
vaUseNoVA funding fee class (VA loans only). Default first.
yearsYesTerm in years, 1 to 50.
ratePctYesAnnual interest rate in percent.
loanTypeNoDefault conventional. FHA, VA and USDA add their standard fees (see sources in the response).
homePriceYesPurchase price.
hoaMonthlyNoMonthly HOA dues.
pmiRatePctNoConventional PMI rate, percent of the loan a year (default 0.6). Applies only above 80% loan-to-value and stops at 78% of the original price.
downPaymentNoDown payment as an amount. Send this or downPaymentPct (default 20%).
yearlyExtraNoOne extra payment every year.
annualIncomeNoGross yearly income, for the debt-to-income check. Send this or monthlyIncome.
compareYearsNoThe two terms to compare, default [15, 30].
extraMonthlyNoExtra principal paid every month.
hoaGrowthPctNoYearly increase of HOA dues in percent.
oneTimeExtraNoOne extra payment.
taxGrowthPctNoYearly increase of property tax in percent; any growth field adds a year-by-year costGrowth table.
includeYearlyNofalse leaves out the year-by-year table.
monthlyIncomeNoGross monthly income.
closingCostPctNoClosing costs as a percent of the price; adds closing costs and cash to close.
downPaymentPctNoDown payment as a percent of the price.
propertyTaxPctNoYearly property tax as a percent of the price. Send this or propertyTaxAnnual.
firstPaymentDateNoDate of the first payment, YYYY-MM-DD. Adds the payoff dates; it only labels the schedule.
otherMonthlyDebtsNoOther monthly debt payments (car, cards, student loans) for the back-end ratio.
propertyTaxAnnualNoYearly property tax as an amount.
insuranceGrowthPctNoYearly increase of insurance (and maintenance) in percent.
maintenanceMonthlyNoMonthly maintenance and other costs (shown in the total, left out of the debt-to-income housing figure).
homeInsuranceAnnualNoYearly homeowners insurance.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this as a safe, read-only, idempotent, non-destructive calculation, so the safety profile is covered. The description adds useful feature context such as taxes, insurance, PMI, HOA, extra payments, biweekly payments, and payoff date, but it does not describe return shape or computational assumptions beyond those phrases.

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

Conciseness5/5

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

The description is a single, front-loaded sentence with zero wasted text. It efficiently lists the calculator's main capabilities in a compact form.

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

Completeness3/5

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

For a complex 26-parameter calculator with nested objects and no output schema, the description covers only the headline capabilities. It does not describe return values, comparison output, debt-to-income behavior, closing-cost output, or other important results, though the full schema compensates substantially for parameter documentation.

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 all 26 parameters are fully documented in the schema. The description adds only high-level feature names and does not add parameter-level meaning beyond what the schema provides, making the baseline 3 appropriate.

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 resource and calculation: mortgage payments including taxes, insurance, PMI, HOA, extra payments, biweekly payments, and payoff date. It is clearly a mortgage calculator. However, it does not explicitly distinguish itself from siblings like calculate_loan or converters_amortization, so sibling differentiation is left to inference.

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?

The mortgage framing implies when the tool is appropriate, but there is no explicit guidance on when to use it versus calculate_loan or converters_amortization. No exclusions, prerequisites, or alternative routing are stated.

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