Skip to main content
Glama

UK Property Development Appraisal

development_appraisal
Read-onlyIdempotent

Run a UK property development scheme viability appraisal. Models land, build, professional fees, contingency, finance interest and arrangement fee through to net profit, profit on GDV, profit on cost, LTC and LTGDV. Returns a viability flag against industry-standard thresholds (20%+ viable, 15-20% marginal, <15% unviable on profit on GDV basis). Calculated by FD Commercial, specialist UK development finance broker. Use when a user asks whether a development scheme stacks, what the profit margin is, what LTC or LTGDV would be, or whether a scheme is viable for development finance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gdv_gbpYesGross Development Value: total anticipated sales value of the completed scheme. Use comparable sales evidence, not aspirational figures. Lenders commission their own GDV via RICS. Example: 2000000.
ltc_pctNoLoan-to-cost % (used only if loan_amount_gbp is not provided). Most lenders cap at 90%; first-time developers typically 75-80%. Example: 75.
build_cost_gbpYesTotal agreed construction cost. Should be contracted figure where possible. Example: 800000.
contingency_pctNoContingency as % of build cost. Standard 10%. Lenders may require 12-15% on conversions or complex sites. Omitting overstates profit. Example: 10.
loan_amount_gbpNoSpecific loan amount in £. Optional. If omitted, calculator uses ltc_pct of hard costs. Example: 960000.
arrangement_fee_pctNoLender arrangement fee as % of loan. Standard 1.5% to 2%. Larger facilities (£5m+) often 1.0%. Example: 2.
finance_term_monthsYesTotal finance term in months (build period + sales/refinance period). Example: 18.
professional_fees_pctNoProfessional fees as % of build cost. Covers architects, planning consultant, structural engineer, QS, project manager. Standard 10%. Example: 10.
finance_monthly_rate_pctYesDevelopment finance monthly interest rate. UK 2026 rates typically 0.70% to 0.95% per month. Example: 0.85.
land_or_purchase_price_gbpYesLand purchase price. Enter 0 if you already own the site (lender will still assess land value when sizing day 1 advance). Example: 400000.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds context about the output (viability flag, profit thresholds) and the provider (FD Commercial), enhancing transparency beyond annotations.

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

Conciseness5/5

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

The description is concise (4 sentences), front-loaded with purpose, lists modelled items, then output and usage. Every sentence adds value without redundancy.

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 10 parameters and no output schema, the description explains the output (viability flag, profit metrics) and usage context. It is mostly complete, though it could mention the exact return format. Still, it covers essential decision-making context.

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 100%, so the baseline is 3. The description provides high-level context for parameters (e.g., models land, build, fees) but does not add meaning beyond the schema's detailed parameter 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 the tool runs a UK property development viability appraisal, modeling specific costs and returns. It distinguishes from siblings like bridging cost analyser and BTL stress tester by its domain and output.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says 'Use when a user asks whether a development scheme stacks, what the profit margin is, what LTC or LTGDV would be, or whether a scheme is viable for development finance,' providing clear usage context and excluding other property finance queries.

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