Skip to main content
Glama
UK Business Tools - Ledgerhall

UK Business Tools - Ledgerhall

Prop Property Comps

prop_property_comps
Read-only

Find comparable UK property sales by postcode using Land Registry Price Paid Data; filter by property type, date and outliers, and optionally enrich results with EPC floor area and price per sq ft.

Instructions

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.

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": {
      "postcode": "<postcode>"
    },
    "name": "prop_property_comps"
  }
}

Input 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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint, and the description adds real behavioral context: limit is capped at 200, filter_outliers applies the 1.5*IQR rule to both stats and the transaction list, IQR trimming requires at least 4 prices, and enrich_epc is slower but returns richer data. The "firehose" note on property_type="ALL" warns of a behavior change. It stops short of describing coverage/truncation behavior for the date window.

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 one-line purpose, then a tight bulleted block whose sentences each carry a decision rule. The nested parentheticals about type codes are slightly dense but nothing is redundant.

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?

With 9 parameters at 11% schema coverage, the description must do heavy lifting and mostly does, and an output schema exists so return values need not be described. The unexplained search_level parameter and the absence of any note on result coverage/capping by months leave an agent guessing on two dimensions of behavior.

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 only 11%, so the description carries most of the burden, and it does explain the three non-obvious switches (property_type codes F/D/S/T/O and ALL, transaction_category A vs None, filter_outliers) plus limit and enrich_epc. However, search_level (default "sector"), months, and address are never explained in the description and are undocumented in the schema, leaving a meaningful gap on a parameter that controls geographic granularity.

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?

Names a specific resource (comparable sales) and its data source (Land Registry Price Paid Data), so the agent knows what comes back. It does not, however, distinguish itself from the sibling prop_ppd_transactions, which an agent could plausibly confuse with this tool given the overlapping transaction-level output.

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?

Guidance is framed almost entirely as parameter semantics (when to pass "ALL", when to set filter_outliers, when to enable enrich_epc) rather than as when-to-use-this-tool-vs-another. No sibling is named as an alternative and no exclusion case is stated, so the agent must infer that this is the comparable/valuation-oriented view.

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

Deploy Server

Other Tools