Skip to main content
Glama

home buying cash needed

home_buying_cash_needed
Read-only

Buying a home in the US, UK, Canada, Australia or Ireland: the cash needed on the day and the monthly cost. Purchase tax from the official schedules with first-time buyer relief (England and NI SDLT, Scotland LBTT, Wales LTT; Canadian land transfer tax or registration fee by province with first-time buyer refunds; Australian transfer duty with each state’s first home buyer concessions; Irish stamp duty, on the VAT-exclusive price for a new home), the CMHC premium and the sales tax on it (Canada), the First Home Owner Grant and 5% Deposit Scheme (Australia), Help to Buy (Ireland), the GST rebate on a new home (Canada), fees (estimates you can pass), the mortgage payment, PMI (US, until 78%), the lender test of the country (US 28/36 rule of thumb, Canadian stress test GDS/TDS, APRA 3-point buffer, Central Bank 4x/3.5x income, UK 4.5x guide), months of saving until the cash is there and the first year buying beats renting (rent vs buy model). Rules read 9 November 2026.

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": {
      "country": "<country>",
      "price": "<price>"
    },
    "name": "home_buying_cash_needed"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateNoMortgage rate, % a year
rentNoRent paid now, a month
termNoMortgage term or amortization, years
priceYesPrice of the home, local currency
incomeNoHousehold gross income a year
regionNoUS state code (AL, AK, AZ, AR, CA, CO, CT, DE, DC, FL, GA, HI, ID, IL, IN, IA, KS, KY, LA, ME, MD, MA, MI, MN, MS, MO, MT, NE, NV, NH, NJ, NM, NY, NC, ND, OH, OK, OR, PA, RI, SC, SD, TN, TX, UT, VT, VA, WA, WV, WI, WY); UK nation (England, Northern Ireland, Scotland, Wales); Canadian province code (ON, ON-TOR, BC, AB, QC, QC-MTL, MB, NB, NS-HFX, PE, SK, NL); Australian state (NSW, VIC, QLD, WA, SA, TAS, ACT, NT); Ireland: leave out
countryYesCountry edition
savingsNoSaved so far
newBuildNoNewly built home (Canada, Australia, Ireland)
firstTimeNoFirst-time buyer (default true)
depositPctNoDeposit or down payment, % of the price (default 10)
monthlySavingNoSaved each month

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with a deterministic, rule-based calculator. It adds genuine context beyond the annotations: the rules snapshot date ('read 9 November 2026'), which reliefs/grants are applied by default, that fees are user-passable estimates, and specific rule mechanics such as PMI ending at 78% and the country-specific lender tests. It does not describe the return shape, but the component list largely stands in for that.

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

Conciseness2/5

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

The content is front-loaded (countries, then headline outputs), but the entire definition is effectively one run-on sentence with a long semicolon-and-parenthesis cascade of tax names. It is compact yet hard for an agent to parse into discrete capabilities, and the jurisdiction-specific detail could be structured or moved behind a shorter summary.

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 12-parameter calculator with no output schema, the description does the required work of enumerating what comes back: purchase tax, grant/rebate effects, fees, mortgage payment, PMI, lender test, months of saving, and the rent-vs-buy crossover. The rules vintage is stated. Missing is the output structure (single summary vs itemised breakdown) and any currency/rounding note, but overall it is sufficient to call the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so 3 is the baseline, but the description exceeds it by mapping inputs to outputs: 'savings' and 'monthlySaving' drive months-of-saving, 'rent' feeds the rent-vs-buy model, 'income' feeds the named lender tests, and 'firstTime'/'newBuild' gate the reliefs. That linkage is meaning the schema does not carry. It still never explains defaults or interactions, e.g. what happens if income is omitted from a stress test.

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 concrete computation (cash needed on the day plus monthly cost) across five named country editions and enumerates the tax/relief/grant/mortgage components it rolls up. An agent can tell it is a full home-purchase cost calculator. It stops short of 5 because it never distinguishes itself from siblings such as uk_stamp_duty_england_ni, scotland_lbtt or wales_ltt, whose subject matter it partly duplicates.

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?

Usage is only implied: an agent can infer 'call this when a user asks what a home purchase costs in one of these five countries'. There is no explicit when-not guidance and no routing to the dedicated single-tax siblings (scotland_lbtt, uk_stamp_duty_england_ni, ireland_help_to_buy), which is a real gap given the overlap.

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.