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 Fox Davidson, whole of market 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.

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": {
      "gdv_gbp": "<gdv_gbp>",
      "land_or_purchase_price_gbp": "<land_or_purchase_price_gbp>",
      "build_cost_gbp": "<build_cost_gbp>",
      "finance_monthly_rate_pct": "<finance_monthly_rate_pct>",
      "finance_term_months": "<finance_term_months>"
    },
    "name": "development_appraisal"
  }
}

Input 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: the returned viability bands (20%+ viable, 15-20% marginal, <15% unviable on profit on GDV basis) and the fact that it computes rather than looks up. It does not say how optional parameters interact beyond what the schema says, and no output schema exists to explain response shape.

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?

Front-loaded with the purpose in the first clause, then outputs, then usage triggers — a sensible order with no filler sentences. The attribution clause ("Calculated by Fox Davidson, whole of market UK development finance broker") is partly marketing but does convey provenance and methodology ownership, so it only marginally costs conciseness.

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 10-parameter calculator with full schema coverage and no output schema, the description covers what an agent needs: what inputs are modelled, which metrics are returned, and how the viability flag is thresholded. It does not specify response units or field naming, but that is a minor residual gap given the schema already documents inputs in detail.

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% and each parameter already carries examples, ranges and lender-standard defaults, so the schema does the heavy lifting. The description's only parameter-level contribution is naming the cost categories modelled, which roughly maps to gdv/build/professional_fees/contingency/finance parameters but adds no syntax or default guidance beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource: "Run a UK property development scheme viability appraisal," then enumerates exactly what is modelled (land, build, fees, contingency, finance interest, arrangement fee) and which metrics come back (net profit, profit on GDV, profit on cost, LTC, LTGDV). No sibling in the list does scheme-level viability, so an agent can route here without opening the schema.

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?

Gives an explicit trigger list: "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." That is clear when-to-use context, but it names no exclusions or alternatives (e.g. when to prefer the bridging loan calculator instead), so it stops short of a 5.

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