UK Property Data

property_blocks

Read-only

Property block analysis — identify buildings with multiple flat sales (block-buy opportunities).

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

Input Schema

Name	Required	Description	Default
`months`	No	Number of calendar months ending today; default 24. Results are limited to available coverage.
`postcode`	Yes
`search_level`	No		sector

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 4, 2026
- 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
```

Changed6 schema fields changedMay 9, 2026

removedInput schema / properties / limit

Removed value: -{
-  "default": 50,
-  "description": "Maximum number of blocks to return (default 50)",
-  "type": "integer"
-}

removedInput schema / properties / min_transactions

Removed value: -{
-  "default": 2,
-  "description": "Minimum sales per building to qualify (default 2)",
-  "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. \"B1 1AA\")"
```

removedInput schema / properties / property_type

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": "F",
-  "description": "PPD property type filter — \"F\" for flats, None for all types (default \"F\")"
-}

removedInput schema / properties / search_level / description

Removed value: -"Search granularity — \"postcode\", \"sector\", or \"district\" (default \"sector\")"

AddedMay 8, 2026
RemovedMay 3, 2026
Changed3 schema fields changedApr 20, 2026
- addedInput schema / properties / min_transactions / description
```
Added value: +"Minimum sales per building to qualify (default 2)"
```
- addedInput schema / properties / months / description
```
Added value: +"Lookback period in months (default 24)"
```
- addedInput schema / properties / postcode / description
```
Added value: +"UK postcode (e.g. \"B1 1AA\")"
```
First observedApr 20, 2026

TDQS

A3.5/5.0

Behavior3/5

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

readOnlyHint=true already covers the read-only nature, so the description doesn't need to restate that. The description adds a bit of behavioral context by indicating the tool identifies buildings with multiple flat sales, but it doesn't disclose important operational traits like data coverage, required postcode format, or the meaning of 'block-buy opportunities' in the output.

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 a single, well-structured sentence that front-loads the tool's domain ('Property block analysis') and then clearly states the objective. Every word earns its place; there is no filler or repetition.

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

Completeness2/5

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

With three parameters and an ambiguous search_level, the description leaves out essential input semantics and any usage context. Although an output schema exists, the agent still needs to understand what a block-buy opportunity looks like and how the parameters shape the analysis, none of which is explained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%, so all three parameters are not adequately documented in the schema. The description provides no additional meaning for 'postcode,' 'months,' or especially 'search_level' (a non-obvious parameter with default 'sector'). This fails to compensate for the low schema coverage.

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 names a specific verb ('identify') and a specific resource ('buildings with multiple flat sales'), and frames the purpose as 'block-buy opportunities.' This clearly separates it from sibling tools like property_comps or property_yield, which focus on valuation and yield rather than block-buy identification.

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 description implies when to use the tool — when the user needs to spot buildings with multiple flat sales for block buying. However, it gives no explicit exclusions or guidance about when to prefer an alternative tool, so the agent must infer the appropriate context from the purpose alone.

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 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.