Market and Regulatory Data Feeds — Zinin M2M Hub

Rightmove UK Property Listings (London and beyond)

rightmove-london

Read-only

Pull live for-sale and to-rent property listings straight from Rightmove.co.uk — the UK's biggest property portal — for London or any other Rightmove location code. No login, no browser, no proxies. — $0.02/call, x402 (USDC on base).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`deal_type`	Yes	"sale" for properties for sale, "rent" for properties to rent.	sale
`max_items`	No	Maximum number of listing rows to return in this run.
`max_pages`	No	How many result pages (24 listings per page, per Rightmove) to walk before stopping.
`location_identifier`	Yes	Rightmove's own opaque location code, format "TYPE^NUMBER" (e.g. "REGION^87490" for London). Rightmove does not publish a name-to-code lookup table; to find the code for another area, search that area on rightmove.co.uk and copy the `locationIdentifier` query parameter from the results page URL.	REGION^87490

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds meaningful extra context: 'No login, no browser, no proxies' explains auth/execution requirements, and '$0.02/call' provides cost transparency not in annotations.

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 one compact sentence with a brief cost note appended; it front-loads the core action and scope. Every segment adds value (source, scope, execution mode, cost), with no fluff.

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?

The tool is a straightforward read-only listing fetcher; annotations and complete schema parameters cover safety and inputs. The description lacks an explicit return-format statement (no output schema exists), but 'property listings' plus the schema's pagination parameters give enough context for selection and invocation.

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%, with detailed explanations for location_identifier, deal_type, max_items, and max_pages. The description adds no new parameter detail beyond what the schema already provides, so baseline 3 is appropriate.

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 uses the specific verb 'Pull' and identifies the resource as 'live for-sale and to-rent property listings straight from Rightmove.co.uk', clearly distinguishing it from sibling country-portal tools. It also states the scope ('London or any other Rightmove location code').

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?

It gives clear context: the tool is for Rightmove UK listings and requires no login/browser/proxies, implying direct API access. It does not explicitly name alternatives or exclusions, but the Rightmove-specific scope and sibling names make the intended use obvious.

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

All Market and Regulatory Data Feeds — Zinin M2M Hub tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0

Disambiguation2/5

Many tools have overlapping purposes, with over a dozen real-estate scrapers and half a dozen job boards differentiated only by geography. While descriptions are clear, an agent would struggle to pick the correct tool without prior knowledge of the specific site or region, leading to frequent misselection.

Naming Consistency2/5

Tool names use a mix of lowercase-hyphenated (boss-az, clinical-trials-monitor), underscore (pricing_info), and long descriptive phrases (official-gazette-regulatory-action-router). No consistent verb_noun pattern exists; some start with source domains, others with action nouns. This lack of predictability makes navigation confusing.

Tool Count3/5

36 tools is on the heavy side for a server that could have been more focused. While a 'data hub' can justify many endpoints, the high number of near-identical scrapers (12+ real estate, 6+ job boards) suggests bloat rather than well-scoped functionality. A leaner set with parameterized regional filters would be more appropriate.

Completeness2/5

The claimed domain 'Market and Regulatory Data Feeds' is poorly served: there are no stock/forex/commodity price feeds, few global regulatory sources (only FDA, SEC, EU tenders), and many tools are for job and property listings which are tangential. The set feels like a random aggregation rather than a coherent surface, with obvious gaps for core market and regulatory data.

Resources

Need Help?