property-search

Sold prices for a UK postcode (HM Land Registry)

get_sold_prices

Read-onlyIdempotent

Recorded sale prices for one full UK postcode in England or Wales, newest first, from HM Land Registry Price Paid data: address, price (GBP), completion date, property type, tenure and whether it was a new build. Returns an attribution statement that MUST be shown with the figures (Open Government Licence). Sale prices only — never ownership records. An empty result means no recorded sales at that exact postcode; try a neighbouring one. Scotland and Northern Ireland are not covered by this data.

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": "get_sold_prices"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	How many sales to return (default 12, max 50)
`postcode`	Yes	Full UK postcode, e.g. "CT21 4DA"

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, but the description adds meaningful behavior beyond them: results are ordered newest first, an attribution statement must be surfaced with the figures, and empty results have a defined meaning. It does not discuss pagination or rate limits, but those are largely moot given the limit cap.

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 and coverage, followed by the returned fields and the legal attribution requirement. Every sentence carries information, though the field enumeration makes it dense and slightly run-on.

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

Completeness5/5

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

With no output schema, the description compensates by enumerating the returned fields (address, GBP price, completion date, property type, tenure, new-build flag) and flags the mandatory attribution statement. Geographic exclusions and the empty-result interpretation close out everything an agent needs before calling.

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 coverage is 100%, so both parameters (postcode, limit) are already documented with examples and bounds. The description reinforces that a single *full* postcode is required, which marginally sharpens the postcode semantics, but says nothing about `limit` beyond supplying the ordering context.

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 (recorded sale prices) with exact scope: one full UK postcode, England or Wales, sourced from HM Land Registry Price Paid data. It also explicitly excludes ownership records, so an agent can distinguish it from a property-details or ownership tool 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 clear usage conditions: requires a full postcode, only covers England and Wales, and explains what an empty result means plus the fallback (try a neighbouring postcode). It lacks explicit routing to a named alternative tool, which keeps it below a 5.

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

All property-search tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?