HOUSE 'N' STARS Real Estate Discovery

Search HOUSE N STARS properties

search_hns_properties

Read-only

Search real public luxury real estate listings from the HOUSE N STARS structured property dataset using server-side WordPress search. Supports free-text criteria and filters for location, property type, Sale/Rent status, price range, bedrooms and result limit. Returns structured listing data including title, location, property type, transaction type, price display, bedrooms, bathrooms, surface, features and public listing URL.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of results to return. Maximum 20.
`query`	No	Free text search, for example sea view, garden, penthouse, waterfront. Do not use this field for sale/rent intent alone; use transaction_type.
`bedrooms`	No	Minimum number of bedrooms requested by the user.
`location`	No	Location filter, for example Dubai, Abu Dhabi, Monaco, Nice, Èze.
`max_price`	No	Maximum price as a number, without currency symbols.
`min_price`	No	Minimum price as a number, without currency symbols.
`property_type`	No	Property type, for example Villa, Apartment, Penthouse, Townhouse.
`transaction_type`	No	Sale/Rent filter. Use exactly Sale for properties for sale and Rent for rental properties. Do not put rent/rental/for rent into query when this parameter is used.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`source`	Yes
`status`	Yes
`filters`	Yes
`results`	Yes
`found_posts`	Yes
`max_num_pages`	Yes
`returned_count`	Yes
`requested_limit`	Yes
`query_posts_count`	Yes
`raw_returned_count`	Yes
`public_response_guidance`	Yes
`ready_to_use_public_table`	Yes
`wordpress_requested_limit`	Yes

TDQS

A4.1/5.0

Behavior4/5

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

Beyond the readOnlyHint and destructiveHint annotations, the description adds concrete behavioral details: it mentions server-side WordPress search, the structured dataset, and the exact set of fields returned in the result. It also implies public listings via 'real public luxury real estate listings' and 'public listing URL', providing useful context not present in the 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 two sentences with no redundant phrases. It front-loads the core action and resource, then briefly lists supported filters and output fields. Every clause contributes useful information, achieving high clarity with minimal length.

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?

Given the presence of a full output schema, the description need not explain return values but does so briefly, reinforcing key fields. Combined with annotations (readOnly, openWorld) and complete parameter documentation, the tool definition leaves no critical gap for an agent to invoke it correctly. It is comprehensive for a read-only search tool.

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 the schema already documents all parameters thoroughly. The description summarizes the filter types ('location, property type, Sale/Rent status, price range, bedrooms and result limit') but does not add new semantic constraints or clarify nuances beyond what the schema provides. This aligns with the baseline 3.

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 a specific verb ('Search'), names the resource ('HOUSE N STARS structured property dataset'), and enumerates the filtering dimensions. It clearly distinguishes the tool from generic search by specifying the dataset source, making the purpose unambiguous.

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 usage context (for searching HOUSE N STARS listings) but does not explicitly state when to prefer this tool over the sibling 'search_properties' or any other alternative. There is no 'use this when...' or 'do not use this for...' guidance, so the agent must infer the appropriate choice from the dataset mention.

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

All HOUSE 'N' STARS Real Estate Discovery 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

A4.1/5.0

Disambiguation3/5

The two search tools, search_hns_properties and search_properties, directly overlap in functionality, with the latter explicitly designated as legacy. While descriptions clarify which to prefer, an agent could easily invoke the wrong one. The other tools (overview, get_property, api_status) are clearly distinct.

Naming Consistency3/5

Naming mixes get_ prefixes with search_ prefixes and one status-style name (hns_api_status). The use of the 'hns' brand prefix is inconsistent across tools, and one tool lacks a verb entirely. Despite this, all names are snake_case and reasonably readable.

Tool Count5/5

Five tools is well-scoped for a real estate discovery server. Each tool serves a clear purpose, with the exception of the legacy duplicate, and the count feels neither thin nor bloated.

Completeness5/5

The read-only discovery domain is well covered: overview explains scope, search handles discovery with filters, get_property retrieves full details, and api_status provides health checking. No significant gaps are apparent for the stated purpose.

Resources

Need Help?