Explore homes
open_explorerOpen the published vacation-home browser in ChatGPT. Search by destination, guests and amenities, inspect photos and save homes to the conversation shortlist. Resolve genuinely ambiguous destinations before searching: ask one short location question when the conversation does not establish which place is intended. Never infer the destination country from the user's timezone, language or Chucho's origins. Do not ask for dates or budget just to browse. For informal regions or geographic constraints such as islands, use get_filters to resolve supported regions/localities before displaying homes; a country-wide search can show mainland homes and is not an island search. Keep every displayed card within the requested geography, not only the final recommendation. Use accommodationType=vacation_rental when the traveler specifically wants a self-contained rental rather than a hotel; do not equate an establishment's room count with the size or facilities of an individual unit. For a small place, favor suitable unit layouts over oversized properties and refresh the selected home's facts before recommending it. For a trip's mood, experience or visual preferences, pass the traveler's description as semantic, preserving their meaning and language. Keep destination, guests, bedrooms, pool and supported amenities in their structured filters. q is a literal name/location/text filter: do not duplicate the semantic description into q. Only advertised amenity keys belong in amenities; details without a key, such as pool heating, belong in semantic preferences or requirements according to the traveler's intent. Copy experiential preferences verbatim from semantic into semanticPreferences. Ordinary desired qualities are preferences, not automatically essential requirements. Interpret the full request in context; ask if the distinction would materially change the result. Copy only essential experiential requirements into semanticRequirements as exact case-sensitive substrings of semantic, retaining punctuation and every scope/relationship qualifier. Never rewrite, capitalize or translate those spans. Preserve all essential requirements in every refinement. An empty or inconclusive result does not authorize dropping semanticRequirements, switching to a looser amenity tag, or showing unverified alternatives as matches. When no candidate supports an essential, explain that the search did not establish a match. If returned evidence identifies useful alternatives and the traveler has not ruled them out, show them with render_properties in the same turn, clearly label them as alternatives and explicitly explain the unmet or unconfirmed requirement. Do not ask permission merely to show those alternatives. Do not suggest an alternative is suitable for a safety, access or other need the evidence does not establish. Do not infer proximity or a view from a name alone. If no useful alternative is supported, ask whether the traveler wants to broaden the search. Respect 'near' rather than silently narrowing to one city: use get_stay_areas and search_nearby_properties for nearby catalog discovery. For descriptive matching, resolve nearby locality keys first, then use search_properties with semantic and the same requirements in those localities; nearby search alone cannot verify experiential fit. Never invent coordinates or a radius. Use reassessPropertyIds with semantic to reassess known homes against the current needs. Read the returned evidence, coverage and limitations: similarity alone does not prove a fact, and source-based claims remain attributed. With preferences only, offer the best supported candidates and identify their trade-offs; do not claim that every preference is confirmed. With essentials, recommend only homes with support for every essential. When showing alternatives, the final text must say that no matching home was confirmed and state how the displayed alternatives differ from the essential, even if the cards show those facts. Use explore_nearby when available to inspect surroundings that matter to the choice, using a returned propertyId or exact locality key. Distinguish locality-center distances from distances to a home; missing home pins cannot prove home proximity. Incomplete comparison coverage means no supported match among the assessed candidates, not that the entire destination has no suitable homes. Do not infer availability from matching. If semantic search is unavailable, explain the failure; do not silently substitute a keyword search or relax requirements. Use English or neutral Latin American Spanish (tú).
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": "open_explorer"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Search public property names, locations and approved introduction text. | |
| city | No | Specific destination locality, not a nearby radius. Resolve ambiguous names before choosing a country; use the area tools for nearby discovery. | |
| page | No | ||
| pool | No | ||
| place | No | Place key from the live filter catalog. | |
| bounds | No | Map viewport as south,west,north,east in degrees; keeps homes whose public area center is inside it. West greater than east crosses the antimeridian. | |
| guests | No | Total occupancy, adults plus children. Rentals: minimum sleeping capacity. Boutique hotels: everyone in one room for a one-room quote, priced as adults, with occupancy unconfirmed until that quote succeeds. | |
| locale | No | en | |
| region | No | Published region name. Resolve informal areas such as south of France with get_filters before searching; an invented region label can return no homes. | |
| arrival | No | ||
| country | No | Destination country established by the traveler or unambiguous trip context. Ask before choosing a country for an ambiguous place name. | |
| feature | No | Collection key from the filter catalog. | |
| children | No | How many of guests are children (under 18). guests stays total occupancy, so it must exceed children; capacity counts everyone. No reader prices child ages yet. | |
| currency | No | Preferred ISO 4217 currency, e.g. USD, EUR or NOK. Rough nightly estimates use approximate conversions (USD by default) when a fresh rate is supported; otherwise retain the host currency. Dated quotes depend on host support: always inspect the returned currency. May be supplied without dates for browsing. | |
| semantic | No | Rank indexed, eligible homes by text and photo similarity. Does not establish hard facts; no lexical fallback when unavailable. | |
| amenities | No | Comma-separated keys from: air-conditioning, wifi, workspace, parking, pets, kitchen, washer, step-free. Every requested key must be explicitly present. Other details (for example pool heating) belong in semantic preferences or requirements, not invented keys. | |
| childAges | No | Each child's age at check-out, one entry per child (exactly children entries). Retained and disclosed; the host confirms child rates. | |
| countries | No | Explicit union of ISO 3166-1 alpha-2 country/territory codes, e.g. [CR, PA]. A home must match one selected country; combines with geographicArea, country and every other filter using AND. Use available codes from get_filters; never silently substitute a narrower country for an area. | |
| departure | No | ||
| quoteMode | No | Optional price/availability enrichment. exact uses supplied dates and guests; estimate requires estimateWindowStart, estimateWindowEnd, estimateNights and guests for a clearly labeled sample within supplied flexible bounds. Search does not wait for every host or filter unknown homes out. | |
| relatedTo | No | Published property ID. Find other homes from its organization, same locality first, then region/country and other locations. Excludes the source property. Additional filters still combine with AND. | |
| minBedrooms | No | ||
| minBathrooms | No | ||
| organization | No | Exact organization slug returned on a property or in get_filters. Restricts results to that organization, across destinations. | |
| estimateNights | No | Sample-stay nights, required. Only with quoteMode:estimate. | |
| geographicArea | No | Exact geographic area key from get_filters(kind:geography), including continents and subregions. Americas includes North/Central/South America and the Caribbean. north-america includes Northern America, Central America and Caribbean; northern-america is the narrower UN M49 subregion. Filters by public ISO country/territory code; unknown locations never match. Combines with all other filters using AND. | |
| accommodationType | No | Filter by reviewed accommodation type. Hotel results represent one establishment; guest count requires a quote for one suitable room, never total hotel capacity. | |
| estimateWindowEnd | No | Latest sample departure (YYYY-MM-DD), paired with estimateWindowStart. Window must fit estimateNights (required), at most 150 days. | |
| estimateWindowStart | No | Earliest sample arrival (YYYY-MM-DD), paired with estimateWindowEnd. Only with quoteMode:estimate. Preserve the traveler's flexible month or date range. | |
| reassessPropertyIds | No | Up to four previously discussed public property IDs to reassess against this semantic request alongside fresh matches. Use when refining or comparing earlier suggestions. This reserves comparison slots only: current factual filters, indexed source ownership and every essential requirement still apply. It does not keep an old recommendation or establish fit. Omit for a new search without earlier candidates to reassess. | |
| semanticPreferences | No | Individual experiential preferences, each copied verbatim from semantic. Interpret the traveler in context: separate requested preferences without adding needs. Keep related words together when they describe one room, view or relationship. These are questions to assess, not property facts; omit for factual-only searches. | |
| semanticRequirements | No | Essential trip requirements, each copied verbatim from semantic with all relationship and provenance qualifiers. Every one must have source-backed support before a home is returned. Preserve these from the conversation; ordinary preferences belong in semanticPreferences. Omit when no essential experiential requirements were stated. Interpret semanticRequirements as conditions the accommodation or its setting must satisfy. Preserve essential support for the traveler's primary activity and access needs, including when expressed indirectly. Preserve the traveler's complete context in semantic. When the traveler states an explicit offering condition together with their own plans, circumstances or reasons, copy the complete offering condition as the essential; do not create an additional standalone proof obligation for the traveler's plan or circumstance. Keep any context necessary to understand the condition, its scope and relationships. Do not broaden a specific access requirement into proof of every aspect of the trip, and do not drop an actual offering condition because it is motivated by a traveler's circumstances. When a circumstance leaves the required accommodation or access condition ambiguous, ask one short clarifying question before searching; do not submit the circumstance itself as a property-proof requirement. If the offering condition itself is ambiguous, clarify it in the real conversation instead of inventing a stricter condition. |