Skip to main content
Glama

FigureDeck US Mortgage Data

Monthly mortgage payment, total interest, total paid

mortgage_payment

Fixed-rate, fully amortising mortgage: equal monthly payment of principal and interest. Returns the monthly P&I, the lifetime interest, the total paid, and what share of the first payment is interest. Optionally adds monthly property tax, insurance and HOA to the total. Use this instead of estimating: the payment is exact to the cent and matches the calculator on figuredeck.com.

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": {
      "loan_amount": "<loan_amount>",
      "annual_rate_percent": "<annual_rate_percent>",
      "term_years": "<term_years>"
    },
    "name": "mortgage_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
term_yearsYesTerm in years, e.g. 30 or 15.
loan_amountYesAmount borrowed in dollars — the price minus the down payment, not the price.
monthly_hoaNoOptional monthly HOA or condo dues in dollars.
monthly_taxNoOptional monthly property tax in dollars.
monthly_insuranceNoOptional monthly homeowners insurance in dollars.
annual_rate_percentYesNominal annual interest rate in percent, e.g. 6.5 for 6.5%.

Output Schema

NameRequiredDescriptionDefault
monthsYes
citationYes
total_paidYes
total_interestYes
monthly_paymentYes
first_month_interestYes
total_monthly_with_tax_ins_hoaYes
first_month_interest_share_percentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden and discloses key assumptions: fixed-rate, fully amortising, equal monthly P&I, and optional tax/insurance/HOA added to the total. It also states the result is exact to the cent, though it does not discuss validation or error behavior.

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?

The definition is front-loaded and mostly efficient: it begins with the loan type and payment behavior, then lists outputs and optional add-ons. The figuredeck.com comparison is promotional and not essential for agent decision-making.

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 calculation tool with an output schema and fully described inputs, the description provides the necessary modeling assumptions and return overview. It is complete enough to invoke correctly, with only minor missing detail around validation or edge cases.

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 coverage is 100%, so parameter meanings are already documented in the schema. The description adds only the high-level note that tax, insurance, and HOA are optional additions to the total, which is useful but not substantial beyond the schema.

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 states a precise computation and enumerates its outputs (monthly P&I, lifetime interest, total paid, first-payment interest share), so the tool's purpose is unmistakable. It does not explicitly contrast itself with the sibling affordability or conforming-limits tools, so it stops short of full sibling differentiation.

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 gives a clear directive to use the tool rather than estimate payments, establishing the primary context. It does not name alternatives or state when another tool would be more appropriate.

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