Skip to main content
Glama

Mortgage calculator

mortgage_calculator
Read-onlyIdempotent

Use this for a monthly mortgage payment: on a price and deposit over a term, at the lowest 2 or 5 year fixed rate or tracker published today for that loan to value, the Bank of England average, or a rate given; with the payment after the deal ends, total interest, monthly overpayments and their saving, and the payment if rates rose 1 to 3 points. Repayment or interest only. Give a price, or a home page address.

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

Input Schema

NameRequiredDescriptionDefault
homeNoA home page address from a search: its price, nation and builder offers are used.
rateNolowest_2_year_fixed
priceNo
depositNoDeposit in pounds.
term_yearsNo
interest_onlyNo
my_deal_yearsNoWith rate my_rate: years at that rate, 0 for the whole term.
deposit_percentNoDeposit as a percent of the price; 10 when neither is given.
my_rate_percentNoWith rate my_rate: the interest rate.
overpay_monthlyNo
my_follow_on_percentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already state readOnlyHint, idempotentHint, non-destructive and closed-world, so the description need not re-argue safety. It adds real behavioral context beyond them: which rate sources are available ('published today', Bank of England average, or a supplied rate), that repayment and interest-only are both supported, and exactly which derived figures come back, which matters since there is no output schema.

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

Conciseness3/5

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

It is short in word count and front-loads the purpose, but it is a single run-on sentence with stacked clauses ('with the payment after the deal ends, total interest, monthly overpayments and their saving, and the payment if rates rose...') that is hard to parse. Splitting purpose, inputs, and outputs into distinct sentences would cost no words and gain clarity.

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 an 11-parameter calculator with no output schema, the description covers the important ground: input modes, rate-source options, repayment vs interest-only, and the full set of returned figures. Gaps remain around default/fallback behavior when neither price nor deposit is supplied and around the follow-on rate parameter, but nothing critical to a correct call is absent.

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 only 45% across 11 parameters, so the description has to carry weight, and it does explain the rate enum semantics and the price-versus-home alternative. However, several parameters stay opaque in both schema and description — notably my_follow_on_percent and how overpay_monthly interacts with the term — so it only partly compensates for the coverage gap.

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 gives a specific verb and resource ('Use this for a monthly mortgage payment') and enumerates what the result contains: payment after the deal ends, total interest, overpayment savings, and rate-rise stress payments. It is clearly distinguishable from mortgage_rates or affordability_calculator, though it never names a sibling to sharpen the boundary.

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 implied by 'Use this for a monthly mortgage payment' plus the input hint 'Give a price, or a home page address,' which is genuinely useful routing between two input modes. There are no explicit exclusions or pointers to the sibling calculators (affordability, buying_costs) that an agent would need to choose correctly.

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