SiteCheck Jobs & Property

UK homes for sale in London from the public rightmove.co.uk

realestate_rightmove_property

Read-only

UK homes for sale in London (first results page, up to 25) from the public rightmove.co.uk search page: address, asking price in GBP, bedrooms, bathrooms, size and summary. Read from the page's embedded JSON; Rightmove has no free public read API. Related tools on this server, for a different need: realestate_auction_com_property when you need HUD homes for sale by online bid in a US state or city; realestate_purplebricks_property when you need recorded UK residential sale prices and dates for one. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "realestate_rightmove_property"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	How many listings, 1 to 25 (default 10)

Output Schema

Name	Required	Description	Default
`count`	No
`source`	No
`listings`	No
`checkedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only declare readOnly and openWorld; the description adds substantial context beyond them: the data comes from an embedded JSON on the page, Rightmove has no free public read API, results are capped to the first page, and the call costs $0.002 USDC via x402 with failures uncharged. That billing and failure behavior is exactly the kind of trait annotations cannot convey.

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?

Front-loads what the tool returns before the scraping caveat, sibling routing, and pricing, each in a single clause. Despite covering four topics, no sentence is redundant.

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?

An output schema exists so return-value detail is unnecessary, and the description still names the fields, the geography constraint, the result cap, the sourcing method, and the cost model. Nothing an agent needs to decide whether to call it or to interpret a zero-result outcome is missing.

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?

Only one optional parameter and schema description coverage is 100% ('How many listings, 1 to 25'), so the schema already carries the semantics. The description's 'up to 25' corroborates the limit but adds nothing new about format or defaults, so the baseline 3 applies.

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 ('UK homes for sale in London ... from the public rightmove.co.uk search page') plus the exact returned fields, and explicitly frames it against named siblings. An agent can distinguish it from realestate_purplebricks_property or realestate_zoopla without opening a schema.

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 routes the agent: use realestate_auction_com_property for HUD/bid listings, realestate_purplebricks_property for recorded sold prices, this tool for live London for-sale listings. Also bounds usage ('first results page, up to 25') so the agent knows it cannot paginate deeper.

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

All SiteCheck Jobs & Property 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?