Skip to main content
Glama

UK Property Data

by io.github.paulieb89

rental_analysis

Read-only

Rental market analysis and achievable rent estimate.

auto_escalate widens the Rightmove search RADIUS when fewer than 5 listings are found (thin market). This is rental-radius escalation and is unaffected by the PPD geography containment: it does not change a postcode's outcode or sector, so it carries none of the limit-dependence that disabled PPD auto-widening. Response includes thin_market, escalated_from, escalated_to fields when escalation occurs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
radiusNo
postcodeYes
auto_escalateNo
purchase_priceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. Changed1 schema field changed
    • addedInput schema / properties / auto_escalate
      Added value: +{
+  "default": true,
+  "type": "boolean"
+}
  2. Changed5 schema fields changed
    • removedInput schema / properties / auto_escalate
      Removed value: -{
-  "default": true,
-  "description": "Widen radius if fewer than 3 listings found (default true)",
-  "type": "boolean"
-}
    • removedInput schema / properties / building_type
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Filter by building type: F=flat, D=detached, S=semi, T=terraced (default all)"
-}
    • removedInput schema / properties / postcode / description
      Removed value: -"UK postcode (e.g. \"NG1 1AA\")"
    • removedInput schema / properties / purchase_price / description
      Removed value: -"Optional purchase price to calculate gross yield"
    • removedInput schema / properties / radius / description
      Removed value: -"Search radius in miles (default 0.5)"
  3. Added
  4. Removed
  5. Changed5 schema fields changed
    • addedInput schema / properties / auto_escalate / description
      Added value: +"Widen radius if fewer than 3 listings found (default true)"
    • addedInput schema / properties / building_type / description
      Added value: +"Filter by building type: F=flat, D=detached, S=semi, T=terraced (default all)"
    • addedInput schema / properties / postcode / description
      Added value: +"UK postcode (e.g. \"NG1 1AA\")"
    • addedInput schema / properties / purchase_price / description
      Added value: +"Optional purchase price to calculate gross yield"
    • addedInput schema / properties / radius / description
      Added value: +"Search radius in miles (default 0.5)"
  6. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The readOnlyHint annotation already indicates a safe read operation, and the description does not contradict it. The description adds valuable behavioral detail beyond the annotation by explaining how auto_escalate widens the search radius, how it differs from PPD auto-widening, and which response fields appear during escalation.

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 compact and front-loads the main purpose, then dedicates a tight paragraph to the auto_escalate edge case. The PPD comparison is jargon-heavy and could be simplified, but it earns its place by clarifying a potentially confusing behavioral nuance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The presence of an output schema reduces the need to explain return values, and the description already discloses escalation-related response fields. However, a required conceptual parameter, purchase_price, is left unexplained, and no guidance is given about radius units or how purchase_price affects the estimate, so completeness is acceptable but not thorough.

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 0%, so the description must compensate for the lack of parameter documentation. It explains auto_escalate in depth and touches on radius, and postcode is contextually obvious, but purchase_price is never mentioned or connected to the tool's purpose. This partial coverage is useful but leaves a real 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 states the tool produces a 'Rental market analysis and achievable rent estimate', which is a specific resource and outcome. It is clear what the tool does, though it uses noun phrases rather than an imperative verb and does not explicitly distinguish it from siblings like property_yield or property_comps.

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 opening sentence implies the tool is for rental market analysis and rent estimation, giving a clear general context. However, there is no explicit guidance about when to choose this tool over related siblings, nor any 'when not to use' conditions; the rest of the description focuses on the auto_escalate parameter.

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