com.housenstars/real-estate-discovery

Tools

• get_hns_dataset_overview

  Explain what the HOUSE N STARS ChatGPT connector provides as a read-only AI-native luxury real estate dataset. Use this when the user asks what HOUSE N STARS covers, what data the app can access, whether it is read-only, which markets are represented, or why the connector is useful inside ChatGPT. This tool summarizes dataset scope and limitations; it does not search individual listings and does not retrieve archival HNS research reports unless dedicated tools are added later.

  shallow
• get_property

  Retrieve one real HOUSE N STARS property by exact numeric ID or exact slug. For normal user-facing answers, summarize the property cleanly. Never add Technical check, Result check, API check, connector check, structuredContent, diagnostics, endpoint details, or implementation notes unless the user explicitly asks for a technical verification.

  shallow
• hns_api_status

  Check whether the HOUSE N STARS WordPress property API is reachable through the Render MCP server.

  shallow
• search_hns_properties

  Preferred HOUSE N STARS property search tool. Search real luxury real estate listings from HOUSE N STARS using server-side WordPress search across the full HNS property database. Use the explicit transaction_type parameter for Sale/Rent distinction: use Sale for properties for sale and Rent for rental properties. Do not express sale/rent intent only as query text. Use price_display for user-facing prices and location for user-facing location names. If price_display is Price on request, present it as POA/price on request. Surface values are raw feed values; do not add sq ft or sqm unless the unit is explicit in the listing text. PUBLIC RESPONSE RULE: for normal property-search answers, use the READY-TO-USE PUBLIC TABLE returned by this tool. Present ALL returned rows up to the requested limit in one compact markdown table. Do not call get_property automatically for each row. Never collapse the answer to only the first listing, never show only two listings, and never say there is only one clear match when more than one result is returned. Do not use image cards or expanded individual property sections for search-result lists because they can cause incomplete answers. Never add a final sentence or paragraph called Technical check, Result check, API check, connector check, tool check, debug note, implementation note, or similar. Do not mention API status, connector internals, filters, diagnostics, structuredContent, returned_count, found_posts, transaction_type, or implementation details unless the user explicitly asks for a technical verification. Present the listings cleanly as real HOUSE N STARS properties.

  shallow
• search_properties

  Legacy compatibility tool for searching HOUSE N STARS properties. Prefer search_hns_properties for new property searches, especially when the user asks for properties for sale or for rent because search_hns_properties exposes transaction_type as the official Sale/Rent parameter. This legacy tool remains available for backward compatibility and uses the same server-side WordPress search, price_display formatting, POA handling, EUR/AED inference, location cleanup and result table output.

  shallow

Embed this server’s score

Tool count and median score across every tool in this server’s corpus — honest in a way a single cherry-picked tool’s badge wouldn’t be.

[![Vouch score](https://vouch.tools/api/servers/a470d1e1-9d37-4c81-9264-85efbc927e4a/badge.svg)](https://vouch.tools/servers/a470d1e1-9d37-4c81-9264-85efbc927e4a)