Skip to main content
Glama

UK Buy-to-Let Stress Tester

btl_stress_tester
Read-onlyIdempotent

Run a UK buy-to-let ICR stress test. Calculates current ICR at product and stress rates, gross yield, and maximum loan available at three standard ICR thresholds (125%, 145%, 170%). Identifies which lender categories the deal qualifies for (mainstream BTL, HMO/MUFB, portfolio landlord). Ownership-aware: personal name uses 5.5% stress rate; limited company uses max of product rate or 5.5%. Calculated by FD Commercial, specialist UK property finance broker. Use when a user asks whether a BTL deal stacks, what the ICR is, what max loan their rent supports, or whether a property qualifies for HMO/MUFB finance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownershipNoBorrower structure. 'personal' uses 5.5% stress rate (HMRC tax exposure makes higher cover required). 'ltd' uses max of product rate or 5.5% (limited company SPV borrower, lower stress rate often allowed).
loan_amount_gbpYesLoan amount being assessed in pounds. Example: 300000.
monthly_rent_gbpYesGross monthly rent in pounds. Use total rent for HMO and MUFB (all rooms / units combined). Example: 2500.
product_rate_pctYesAnnual product (pay) rate as a percentage. The actual rate the borrower would pay. Example: 5.5 for 5.5% per year.

TDQS

A4.5/5.0
Behavior5/5

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

Annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false) align with a safe calculation. The description adds critical details: stress rate variations by ownership (5.5% personal vs max(product rate, 5.5%) for ltd), lender category identification, and calculation source. No contradictions.

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 description is front-loaded with the main purpose and then provides structured detail. It is slightly verbose but every sentence adds value. Could be trimmed slightly, but overall efficient.

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?

Given 4 parameters with 100% schema coverage and no output schema, the description adequately covers the tool's computation and interpretations. It lists what is calculated, though it doesn't describe the exact output format. Still, it provides sufficient context for invocation.

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 description coverage is 100%, providing a baseline of 3. The description adds value by explaining the ownership parameter's effect on stress rate and clarifying that monthly_rent should be total for HMO/MUFB, going beyond the schema's basic descriptions.

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 clearly states 'Run a UK buy-to-let ICR stress test' and enumerates specific outputs (ICR, yield, max loan, lender categories). It is easily distinguished from sibling tools which are bridging, development, and stamp duty calculators.

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?

Explicitly describes when to use the tool: when a user asks about BTL deal viability, ICR, max loan, or HMO/MUFB qualification. While it doesn't explicitly state when not to use it, the sibling tools are sufficiently different to imply appropriate context.

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.

TDQS

A4.5/5.0
Disambiguation5/5

Each tool targets a distinct UK property finance scenario: bridging loans, BTL stress testing, development appraisal, and stamp duty. There is no overlap in their purposes.

Naming Consistency5/5

All tool names use descriptive snake_case with a consistent pattern: noun_verb_analyser/calculator/tester/appraisal. The naming is clear and predictable.

Tool Count5/5

With 4 tools covering core property finance calculations, the count is well-scoped for the server's purpose. Each tool provides essential functionality without being overly narrow or broad.

Completeness4/5

The tools cover major areas of UK property finance (bridging, BTL, development, stamp duty). Missing are general mortgage affordability or commercial property calculators, but the set is complete for the stated focus on specialist broker calculations.

Resources