Skip to main content
Glama

Mortgage rates by lender

mortgage_rates
Read-onlyIdempotent

Use this for UK lenders' current published mortgage rates, as NewHomeSearch holds them with the date each was read: each product's initial rate, follow-on rate, APRC, maximum loan to value and fees, with a link to the lender's own page; for a price and deposit, the monthly payment and APRC for that loan. Filter by fixed or tracker, deal length, first time buyer or mover, and lender. Recent rate changes too. Listed by lender, not ranked. Information only: it gives no mortgage advice, recommends no product and arranges no mortgage.

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_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoany
buyerNofirst_time_buyer
priceNo
yearsNoDeal length in years.any
lenderNoOne lender by name, for example Nationwide.
changesNoAlso list rate changes in the last five weeks.
depositNo
term_yearsNo
deposit_percentNo10 when no deposit is given.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive and closed-world behavior, so the description's contribution is extra context: each rate carries the date it was read (freshness), results are unranked and listed by lender, and the tool is explicitly non-advisory. It does not say how many products are returned or whether results are truncated, which is the main missing behavioral detail.

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 purpose is front-loaded in the first clause, followed by what is returned, then filters, then the caveat. It is dense and clause-heavy rather than wasteful, but the single sprawling sentence could be split for faster scanning.

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 nine-parameter, no-output-schema, mostly-optional read tool, the description covers purpose, returns, filters, freshness and disclaimers, which is close to sufficient. It is missing only result size/ordering mechanics and any hint about what happens when optional filters are omitted.

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 only 44%, so the description must carry weight, and it does: it maps fixed/tracker, deal length, first-time-buyer vs mover, lender, price and deposit (yielding a monthly payment and APRC for that loan), and the rate-changes flag. Only term_years and deposit_percent are left to the schema, so most of the nine parameters gain meaning from the description.

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?

"Use this for UK lenders' current published mortgage rates" names a specific resource and scope, then enumerates exactly what is returned per product (initial rate, follow-on rate, APRC, max LTV, fees, lender link). It also disambiguates positioning against siblings with "Listed by lender, not ranked" and "Information only: it gives no mortgage advice, recommends no product and arranges no mortgage."

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 clear selection context: use for published lender rates, with filters by type, deal length, buyer type and lender, plus "Recent rate changes too" for the changes flag. It does not explicitly name when to prefer mortgage_calculator or affordability_calculator instead, which is the one remaining gap given the overlapping monthly-payment capability.

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