Skip to main content
Glama

UK Property Data

by io.github.paulieb89

property_yield

Read-only

Gross rental yield for a UK postcode.

Combines Land Registry sale comps (median sale price) with Rightmove rental listings (median monthly rent) to produce a gross yield percentage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
monthsNoNumber of calendar months ending today; default 24. Results are limited to available coverage.
postcodeYesUK postcode (e.g. "NG1 2NS").
search_levelNoPPD search granularity — "postcode", "sector" (default), or "district".sector
auto_escalateNoCompatibility parameter. Does NOT widen the search area on the live source (see `warnings`); previously postcode→ sector→district. Default True. Set False for strict-locality only.
property_typeNoFilter sales by type. None (default) = residential set (F+D+S+T). Pass "F"/"D"/"S"/"T"/"O" for one type, "ALL" for firehose.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • changedInput schema / properties / months / description
      Previous value: -"PPD sale lookback period (default 24)."New value: +"Number of calendar months ending today; default 24. Results are limited to available coverage."
    • addedInput schema / properties / months / minimum
      Added value: +1
  2. Changed1 schema field changed
    • changedInput schema / properties / auto_escalate / description
      Previous value: -"Widen the PPD search area on thin markets — postcode→\nsector→district. Default True. Set False for strict-locality only."New value: +"Compatibility parameter. Does NOT widen the search area on\nthe live source (see `warnings`); previously postcode→\nsector→district. Default True. Set False for strict-locality only."
  3. Changed5 schema fields changed
    • addedInput schema / properties / auto_escalate
      Added value: +{
+  "default": true,
+  "description": "Widen the PPD search area on thin markets — postcode→\nsector→district. Default True. Set False for strict-locality only.",
+  "type": "boolean"
+}
    • addedInput schema / properties / months / description
      Added value: +"PPD sale lookback period (default 24)."
    • addedInput schema / properties / postcode / description
      Added value: +"UK postcode (e.g. \"NG1 2NS\")."
    • addedInput schema / properties / property_type / description
      Added value: +"Filter sales by type. None (default) = residential set\n(F+D+S+T). Pass \"F\"/\"D\"/\"S\"/\"T\"/\"O\" for one type, \"ALL\" for firehose."
    • addedInput schema / properties / search_level / description
      Added value: +"PPD search granularity — \"postcode\", \"sector\" (default),\nor \"district\"."
  4. Changed5 schema fields changed
    • removedInput schema / properties / months / description
      Removed value: -"Sales lookback period in months (default 24)"
    • removedInput schema / properties / postcode / description
      Removed value: -"UK postcode (e.g. \"NG11\", \"SW1A 1AA\")"
    • removedInput schema / properties / property_type / description
      Removed value: -"Filter comparable sales by type: F=flat, D=detached, S=semi, T=terraced (default all)"
    • removedInput schema / properties / radius
      Removed value: -{
-  "default": 0.5,
-  "description": "Rental search radius in miles (default 0.5)",
-  "type": "number"
-}
    • removedInput schema / properties / search_level / description
      Removed value: -"\"sector\" (recommended), \"district\", or \"postcode\""
  5. Added
  6. Removed
  7. Changed5 schema fields changed
    • addedInput schema / properties / months / description
      Added value: +"Sales lookback period in months (default 24)"
    • addedInput schema / properties / postcode / description
      Added value: +"UK postcode (e.g. \"NG11\", \"SW1A 1AA\")"
    • addedInput schema / properties / property_type / description
      Added value: +"Filter comparable sales by type: F=flat, D=detached, S=semi, T=terraced (default all)"
    • addedInput schema / properties / radius / description
      Added value: +"Rental search radius in miles (default 0.5)"
    • addedInput schema / properties / search_level / description
      Added value: +"\"sector\" (recommended), \"district\", or \"postcode\""
  8. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is known. The description adds useful methodology context by naming the two data sources and the calculation, but it does not disclose coverage limitations, fallback behavior, or any caveats about data availability beyond what the schema's parameter descriptions already mention.

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 compact and front-loaded with the core purpose, followed by one sentence explaining the methodology. Every sentence earns its place, and there is no redundant or filler content.

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 the detailed input schema, the readOnly annotation, and the presence of an output schema, the description provides enough context for an agent to understand what the tool computes and how to invoke it. It lacks only minor guidance on data coverage edge cases, which is partially addressed in schema parameter descriptions.

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 every parameter is already documented in the schema. The description does not add much parameter-level meaning, but it doesn't need to because the schema descriptions are already detailed enough.

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 states a specific operation: computing gross rental yield for a UK postcode by combining Land Registry sale comps with Rightmove rental listings. This clearly identifies the resource and output, and the mention of both data sources helps distinguish it from siblings like ppd_transactions, property_comps, or rental_analysis.

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?

The intended use case is implied: when you need gross rental yield for a UK postcode. However, the description does not explicitly state when to prefer this tool over sibling tools, nor does it provide exclusion criteria or alternative routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All UK Property Data toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

EPC coverage is split across property_epc, property_epc_summaries, epc_certificate, and the deprecated property_epc_search, but each has a distinct role (aggregate lookup, candidate list, direct certificate, legacy). Land Registry data is similarly split between ppd_transactions and property_comps with clear output differences; no two tools are truly interchangeable.

Naming Consistency3/5

Names are readable and consistently lowercase snake_case, but they mix resource nouns (epc_certificate, stamp_duty), prefixed nouns (property_epc_summaries, rightmove_listing), and noun-verb forms (company_search, planning_search). The 'search' suffix is used for different actions, and there is no uniform verb_noun pattern across the set.

Tool Count4/5

14 tools is within the appropriate range for a multi-source property data API. The count is slightly padded by the deprecated property_epc_search and the narrowly scoped planning_search/company_search, but most tools cover distinct data products.

Completeness4/5

The set covers the core property workflows: Rightmove listing discovery/detail, EPC search/detail, Land Registry transactions/comps, yield/rent analysis, stamp duty, and planning portal lookup. Minor gaps exist (no planning application details, no property-level title/ownership lookup), but agents can complete common research tasks without dead ends.

Resources