Skip to main content
Glama

UK Property Data

by io.github.paulieb89

property_comps

Read-only

Comparable sales from Land Registry Price Paid Data.

Defaults return the standard residential set:

  • property_type=None means residential (F+D+S+T). Pass "F"/"D"/"S"/"T"/"O" for a single type, or "ALL" to disable type filtering (firehose).

  • transaction_category defaults to "A" (standard sales). Pass None to include category-B (bulk transfers, non-standard conveyances).

  • filter_outliers=False by default; set True for IQR-trimmed stats AND transaction list (1.5*IQR rule, needs >=4 prices).

limit caps returned transactions (max 200). enrich_epc attaches EPC floor area and price-per-sqft to each transaction — slower but richer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
monthsNoNumber of calendar months ending today; default 24. Results are limited to available coverage.
addressNo
postcodeYes
enrich_epcNo
search_levelNosector
property_typeNo
filter_outliersNo
transaction_categoryNoA

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
    • addedInput schema / properties / months / description
      Added value: +"Number of calendar months ending today; default 24. Results are limited to available coverage."
    • addedInput schema / properties / months / minimum
      Added value: +1
  2. Changed2 schema fields changed
    • addedInput schema / properties / filter_outliers
      Added value: +{
+  "default": false,
+  "type": "boolean"
+}
    • addedInput schema / properties / transaction_category
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": "A"
+}
  3. Changed2 schema fields changed
    • addedInput schema / properties / enrich_epc
      Added value: +{
+  "default": false,
+  "type": "boolean"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 50,
+  "type": "integer"
+}
  4. Changed8 schema fields changed
    • removedInput schema / properties / address / description
      Removed value: -"Optional street address to identify subject property and show percentile rank"
    • removedInput schema / properties / auto_escalate
      Removed value: -{
-  "default": true,
-  "description": "Widen search area if fewer than 5 results (default true). Set false to keep results local — useful when district-level escalation would include irrelevant areas.",
-  "type": "boolean"
-}
    • removedInput schema / properties / enrich_epc
      Removed value: -{
-  "default": true,
-  "description": "Add floor area, price/sqft, and EPC rating to each comp (default true)",
-  "type": "boolean"
-}
    • removedInput schema / properties / limit
      Removed value: -{
-  "default": 30,
-  "description": "Max transactions to return (default 30)",
-  "type": "integer"
-}
    • removedInput schema / properties / months / description
      Removed value: -"Lookback period in months (default 24)"
    • removedInput schema / properties / postcode / description
      Removed value: -"UK postcode (e.g. \"SW1A 1AA\", \"NG11 9HD\")"
    • removedInput schema / properties / property_type / description
      Removed value: -"Filter by type: F=flat, D=detached, S=semi, T=terraced (default all)"
    • removedInput schema / properties / search_level / description
      Removed value: -"Search area granularity - usually leave as default"
  5. Added
  6. Removed
  7. Changed8 schema fields changed
    • addedInput schema / properties / address / description
      Added value: +"Optional street address to identify subject property and show percentile rank"
    • addedInput schema / properties / auto_escalate / description
      Added value: +"Widen search area if fewer than 5 results (default true). Set false to keep results local — useful when district-level escalation would include irrelevant areas."
    • addedInput schema / properties / enrich_epc / description
      Added value: +"Add floor area, price/sqft, and EPC rating to each comp (default true)"
    • addedInput schema / properties / limit / description
      Added value: +"Max transactions to return (default 30)"
    • addedInput schema / properties / months / description
      Added value: +"Lookback period in months (default 24)"
    • addedInput schema / properties / postcode / description
      Added value: +"UK postcode (e.g. \"SW1A 1AA\", \"NG11 9HD\")"
    • addedInput schema / properties / property_type / description
      Added value: +"Filter by type: F=flat, D=detached, S=semi, T=terraced (default all)"
    • addedInput schema / properties / search_level / description
      Added value: +"Search area granularity - usually leave as default"
  8. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, so the description carries the behavioral burden and does so thoroughly. It discloses default property filtering, category handling, IQR outlier trimming with a minimum-price requirement, a max limit of 200, and the performance tradeoff of enrich_epc.

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 front-loaded with the core purpose and then uses a tightly scoped bullet list for parameter defaults. Every sentence carries meaningful configuration detail without redundancy or fluff.

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 complexity of 9 parameters and very low schema coverage, the description covers most critical behavior and even notes performance implications. It is not fully complete because address and search_level are left undefined, and no explicit guidance is given for choosing this instead of the related ppd_transactions tool.

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 only 11%, and the description compensates for most key parameters: property_type values, transaction_category defaults, filter_outliers behavior, limit cap, and enrich_epc meaning. However, address and search_level remain semantically unexplained in both schema and description, leaving a gap.

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 clearly states the tool returns comparable sales from Land Registry Price Paid Data, which is a specific resource and function. It lacks an explicit contrast with sibling tools like ppd_transactions, but the 'comparable sales' framing and residential defaults make the core purpose unambiguous.

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?

The description provides clear operational context by explaining defaults for property_type, transaction_category, filter_outliers, limit, and enrich_epc. It does not explicitly say when to prefer this tool over a sibling, but the usage behavior is concrete and actionable.

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