mcp-livedatapro

getRealEstateStats

Residential property prices per sqm/sqft, gross rental yields, cap rates, and inventory by ZIP/postcode. Use when analyzing residential housing market metrics (median price per sqm, home values, 2-bed monthly rent, gross rental yield, and active inventory) by country and postal/ZIP code. Do not use for commercial office/warehouse leases (use getCommercialRealEstate) or short-term hotel stays (use getHotelAvailability).

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": {
      "country_code": "<country_code>",
      "zip_code": "<zip_code>"
    },
    "name": "getRealEstateStats"
  }
}

Input Schema

Name	Required	Description	Default
`zip_code`	Yes	Target postal code, outward postcode, or 5-digit ZIP code (e.g., SW1A, 10001, 1051).
`country_code`	Yes	2-letter uppercase ISO country code (e.g., GB, US, DE, HU, ES).

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 24, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / country_code / examples
```
Added value: +[
+  "GB"
+]
```
- addedInput schema / properties / country_code / pattern
```
Added value: +"^[A-Z]{2}$"
```
- addedInput schema / properties / zip_code / examples
```
Added value: +[
+  "SW1A"
+]
```
- addedInput schema / properties / zip_code / minLength
```
Added value: +2
```

Changed2 schema fields changedOct 24, 2026

changedInput schema / properties / country_code / description

Previous value: -"2-letter ISO country code (e.g., UK, US, DE, HU, ES)"New value: +"2-letter uppercase ISO country code (e.g., GB, US, DE, HU, ES)."

changedInput schema / properties / zip_code / description

Previous value: -"Postal or ZIP code of the target area"New value: +"Target postal code, outward postcode, or 5-digit ZIP code (e.g., SW1A, 10001, 1051)."

First observedOct 21, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description must carry behavioral disclosure. It implies a read-only lookup and lists what data comes back, but says nothing about rate limits, permission/plan requirements, or coverage gaps (e.g., missing ZIPs). Adequate but with clear gaps for an unannotated tool.

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?

Three sentences, front-loaded with the metric list, then usage condition, then exclusions. No filler; every clause carries routing or content information.

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?

Simple two-parameter read tool with no output schema and no annotations; the description compensates by listing the returned metric set. Minor gap: no note on granularity, units, or behavior when a postcode has no data.

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 100%, so both parameters (zip_code, country_code) are already well documented with formats and examples. The description adds only the scoping phrase 'by country and postal/ZIP code', which is baseline-level value.

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/resource combination and enumerates the exact metrics returned (price per sqm/sqft, gross rental yield, cap rate, inventory). It is clearly distinguishable from getCommercialRealEstate and getHotelAvailability, which it names directly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use (residential housing market metrics by country and postal code) and when not to use, naming the two sibling alternatives to route to instead. Nothing is left to inference.

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

All mcp-livedatapro 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?