Skip to main content
Glama

Calculate mortgage payment

spur_calculate_mortgage
Read-onlyIdempotent

Estimate the monthly payment on a home the way Zillow's mortgage calculator does: principal & interest, PMI, property tax, homeowners insurance and HOA, plus total interest and a yearly amortization schedule. Free and runs instantly.

Pass home_price, or property_id to use a saved Spur property's price (falls back to its Zestimate). Anything left out uses these defaults: 20% down, 30-year fixed, 6.25% rate, property tax 1.1% of price/yr, insurance 0.5% of price/yr, PMI 0.5% of the loan/yr when under 20% down (dropped at 78% loan-to-value). The default rate is a placeholder, not a live quote: tell the user which defaults were used and use their own rate when they give one.

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": "spur_calculate_mortgage"
  }
}

Input Schema

NameRequiredDescriptionDefault
pmi_rateNoPMI as % of the loan per year
home_priceNoPurchase price, USD
term_yearsNoLoan term in years (common: 30, 20, 15, 10)
hoa_monthlyNoHOA dues per month, USD
include_pmiNoForce PMI on or off; by default it applies under 20% down
property_idNoSaved Spur property id; its price is used when home_price is omitted
down_paymentNoDown payment in USD (wins over down_payment_percent)
interest_rateNoAnnual interest rate in percent, e.g. 6.5
show_scheduleNoInclude the year-by-year amortization table in the reply
property_tax_rateNoProperty tax as % of price per year
property_tax_annualNoProperty tax per year, USD (wins over property_tax_rate)
down_payment_percentNoDown payment as % of price
home_insurance_annualNoHomeowners insurance per year, USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, so the description isn't burdened with safety disclosure; instead it adds genuinely useful behavior: the default assumption set, the PMI drop rule at 78% LTV, and the warning that the default 6.25% rate is a placeholder rather than a live quote. The only gap is that it doesn't describe response shape beyond listing figures.

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?

Two short paragraphs, front-loaded with what the tool computes, followed by input/default mechanics. The 'Free and runs instantly' clause is mild marketing filler, and the default-rate caveat is slightly repetitive with the defaults sentence, but overall there is little waste.

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 13-parameter calculation tool with no output schema, the description does the needed work: it lists the output components and the amortization schedule option, plus the full default assumption model. Missing only a note on rounding/currency or how the Zestimate fallback behaves when neither price source resolves.

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 every one of the 13 parameters is already documented, which sets the baseline at 3. The description does add value by spelling out the concrete default values (20% down, 30-year, 6.25%, 1.1% tax, 0.5% insurance, 0.5% PMI) and the home_price/property_id precedence, but it does not explain the rate-override or include_pmi interactions beyond what the schema implies.

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?

The description opens with a specific verb and resource ('Estimate the monthly payment on a home') and enumerates exactly what the estimate breaks out (P&I, PMI, tax, insurance, HOA, total interest, amortization). It also names the analog (Zillow's mortgage calculator), which anchors the scope without ambiguity.

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?

It states the two entry paths explicitly ('Pass home_price, or property_id ... falls back to its Zestimate') and describes fallback behavior for anything omitted. It also gives a caller-facing instruction ('tell the user which defaults were used and use their own rate when they give one'), but it never says when not to use this tool or what alternative to pick for a real quote.

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