Skip to main content
Glama

Amortiza Loan Planner

Calculate loan or mortgage

calculate_loan
Read-onlyIdempotent

Use this when the user wants a mortgage calculator, loan calculator, or amortization calculator result: the monthly (or biweekly/weekly) payment, an amortization schedule or table, total interest, payoff date, a mortgage calculator with extra payments or for paying off early, or a full PITI payment with property tax, insurance, HOA and PMI. Takes the loan amount or home price with down payment, rate, and term. Returns exact payment, totals, interest and time saved by extra payments, a yearly summary, and a CSV of the full schedule. Fixed-rate loans only; does not model adjustable rates, interest-only or balloon loans, and does not look up current rates. Do not use for rent-vs-buy advice or choosing a lender.

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

Input Schema

NameRequiredDescriptionDefault
currencyNoISO 4217 currency code for formatting, e.g. USD, EUR, GBP. Default USD.
pmi_rateNoYearly private mortgage insurance rate as a percent of the original loan, e.g. 0.5. Needs home_price. Charged only while the loan is above 80% of the home value, and dropped once the balance reaches 78%.
principalNoLoan amount to borrow, e.g. 350000. Give this OR home_price with a down payment.
home_priceNoPurchase price or current home value, e.g. 400000. Used with down_payment/down_payment_percent to get the loan amount, and as the value for PMI loan-to-value.
start_dateNoDate of the first payment, YYYY-MM or YYYY-MM-DD, e.g. 2026-11. Defaults to the first day of next month.
term_yearsNoLoan term in years, e.g. 30. Give term_years or term_months.
acceleratedNoFor biweekly/weekly only: true pays half (biweekly) or a quarter (weekly) of the monthly payment each period, which adds about one extra monthly payment a year. Default false (a true biweekly/weekly amortization).
annual_rateNoAnnual interest rate in percent (nominal APR used for the payment), e.g. 6.5 for 6.5%. 0 is allowed.
hoa_monthlyNoMonthly HOA dues, e.g. 75.
term_monthsNoLoan term in months, e.g. 360 or 72 for a car loan.
down_paymentNoDown payment amount, e.g. 50000. Used with home_price.
extra_paymentNoExtra principal paid with every payment, e.g. 200 for $200 more each month.
one_time_paymentsNoLump-sum extra payments, e.g. [{"date":"2030-01","amount":10000}].
payment_frequencyNoHow often payments are made: monthly (default), biweekly (every 2 weeks, 26 a year), or weekly (52 a year).
property_tax_annualNoYearly property tax for the PITI breakdown, e.g. 4800.
down_payment_percentNoDown payment as a percent of home_price, e.g. 20 for 20%.
home_insurance_annualNoYearly homeowners insurance for the PITI breakdown, e.g. 1500.

Output Schema

NameRequiredDescriptionDefault
pmiYes
pitiYes
chartYes
inputsYes
yearlyYes
paymentYes
summaryYes
currencyYes
warningsYes
downloadsYes
total_pmiYes
home_priceYes
total_paidYes
vs_monthlyYes
acceleratedYes
annual_rateYes
loan_amountYes
payoff_dateYes
term_monthsYes
final_paymentYes
extra_paymentsYes
payments_countYes
total_interestYes
total_principalYes
payment_frequencyYes
first_payment_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/closed-world, so the description doesn't need to restate safety. It earns credit for disclosing model scope limits beyond the annotations: fixed-rate only, no ARMs, no interest-only or balloon loans, and no live rate lookup. It could go further on how extra/one-time payments interact, but the scope boundaries are the more important disclosure for a calculator.

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?

Front-loaded with the trigger phrase and organized as use cases, then inputs, then outputs, then exclusions. It is dense and appropriately sized for a 17-parameter tool, but the opening enumeration ('mortgage calculator, loan calculator, or amortization calculator result...') reads as keyword-stacked and could be tightened without losing information.

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

Completeness5/5

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

With 17 optional parameters, an output schema, and full annotation coverage, this description supplies everything else an agent needs: when to use it, what inputs it takes, what it returns, and the model's hard limits. No material gap remains for correct invocation.

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 baseline is 3 and the schema already carries per-parameter meaning including examples and the principal-vs-home_price tradeoff. The description adds a modest restatement ('loan amount or home price with down payment, rate, and term') and signals the PITI inputs, but says nothing about extra_payment, one_time_payments, payment_frequency, or accelerated. It does not meaningfully exceed the schema's own documentation.

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 names the exact resource and the concrete outputs an agent can expect: monthly/biweekly/weekly payment, amortization schedule, total interest, payoff date, PITI breakdown, and CSV. An agent can match a user request to this tool without opening the schema. The only thing it does not do is name the compare_loans sibling, but the output enumeration is specific enough to make the tool's identity unambiguous.

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 trigger ('Use this when the user wants a mortgage calculator...') and firm exclusions ('Fixed-rate loans only; does not model adjustable rates, interest-only or balloon loans', 'Do not use for rent-vs-buy advice or choosing a lender'). What's missing is the positive routing to the alternative: compare_loans is never mentioned, so an agent asked to compare two loans has to infer that this tool is not the right one.

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