Skip to main content
Glama

How much can I borrow

affordability_calculator
Read-onlyIdempotent

Use this for how much someone can borrow for a mortgage and the price that reaches: from household income, deposit and monthly commitments, at the income multiples most lenders use and the higher multiple some offer, with the monthly repayment and a stress test. Give a price to check whether it is within reach.

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": {
      "household_income": "<household_income>",
      "deposit": "<deposit>"
    },
    "name": "affordability_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
flatNoThe home is a flat; some lenders lend less on flats.
jointNoTwo buyers applying together.
priceNoA price to check, such as a home’s asking price.
depositYes
term_yearsNo
first_time_buyerNo
household_incomeYesGross income a year, all buyers together.
monthly_commitmentsNoLoans, cards and other monthly debts.

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?

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world calculation, so the bar is lower. The description nonetheless adds real behavioural context: the result is derived using standard lender income multiples plus a higher multiple some lenders offer, and a stress test is applied. That tells the agent the output is modelled, not a guaranteed offer.

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?

The core purpose is front-loaded in the first clause, which is good, but phrasing like "the price that reaches" is awkward and the trailing "Give a price to check whether it is within reach" restates what the opening already implied. It is serviceable rather than tight.

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?

There is no output schema, so the description carries the burden of describing returns, and it does list the key results: maximum borrowing, the price that corresponds, monthly repayment and a stress test. What is missing is any indication of how the affordability verdict or errors are surfaced, but for a calculator of this size it is largely complete.

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 63%, so the schema already documents most parameters; the description adds the modelling context of income multiples and a stress test rather than parameter-level meaning. It names income, deposit, commitments and price as drivers but says nothing about the undocumented booleans (joint, flat, first_time_buyer) or term length, so it only partially compensates.

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 specific verb-plus-resource: it computes how much someone can borrow for a mortgage and the maximum price that follows from income, deposit and commitments. It also enumerates the derived outputs (monthly repayment, stress test), which distinguishes it in substance from repayment-oriented siblings. It never names a sibling, though, so the boundary with mortgage_calculator must be inferred.

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?

"Use this for how much someone can borrow" plus "Give a price to check whether it is within reach" implies the use case, but there is no explicit when-not guidance and no alternative tool is named. Given close siblings such as mortgage_calculator and mortgage_rates, an explicit routing sentence would materially help.

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