NEBLES

Get deep details for ONE specific NEBLES property by its id. Use this for EVERY follow-up about a room the user already picked or that was already shown — LANGUAGE LOCK: answer in the language of the user's latest message only; an English latest message requires an English-only response, regardless of Thai account, browser, profile, or prior conversation context. deposit / total move-in cost, free WiFi & other amenities, building facilities (pool, gym), map/location, pet policy, house rules, full pricing by lease length, move-in date, how to book, photos/video. Reuse the property id and lease length already in the conversation; do NOT call search_properties again for these follow-ups. If the user says option 2/second room, resolve that option from the latest displayed room list only. If the latest list has fewer than that many rooms, ask which previous room they mean instead of guessing from an older list. Pass durationMonths and moveInDate when known so the quote matches and the booking link is prefilled — the user should not have to re-enter them on the website.

get_property_details

Answer general questions about how NEBLES works (not tied to one room): how to rent, whether you pay first and how much, deposits, fees, what 'available' means, service area, and support. LANGUAGE LOCK: answer in the language of the user's latest message only; an English latest message requires an English-only response, regardless of Thai account, browser, profile, or prior conversation context. Use this for process/FAQ questions like 'how do I rent?', 'do I pay first?', 'how much deposit?', 'do you have rooms available?'.

get_rental_info

Search availability-checked NEBLES monthly rental condos in Bangkok. Use this ONLY to start a NEW search or browse. LANGUAGE LOCK: answer in the language of the user's latest message only; an English latest message requires an English-only response, regardless of Thai account, browser, profile, or prior conversation context. CRITICAL: requires budget, lease duration, and location intent — ask a clarifying question first if anything is missing. A broad request like 'Find me a condo in Sukhumvit' is missing budget and lease duration, so do not call this tool yet. Never invent or assume a budget or duration the user did not state. STRICT SCOPE POLICY: never broaden, change, or fallback to another location/transit scope on your own. If a search has 0 or too few rooms, ask the user before widening radius, changing stations, changing zone, or searching all Bangkok. Location modes (pick ONE area mode; PROJECT may stand alone or combine with one): PROJECT — when the user names a condo project/brand (e.g. 'Park Origin', 'Noble ReD'), pass projectName with that text; the server returns every matching branch — never convert a project into stations or lat/lng, and never ask which branch first. AREA GEO — for zones/landmarks, resolve to Bangkok lat+lng and pass lat/lng (text alone is invalid). TRANSIT — for BTS/MRT/ARL/SRT stations or whole lines, pass transitTargets=[{system,name}] with raw names or [{system,line}] for line/color scope (server resolves them; omit name+line only for a whole operator; do not pass lat/lng). ANY AREA — only if the user explicitly says anywhere: anyArea=true plus a transit constraint. Transit distances: near/ใกล้/附近/近く/close to/nearby/walking distance = within 1000m (transitPreference='near'), adjacent/ติดรถไฟฟ้า = within 500m. Near is ALWAYS 1000m even with multiple stations/systems/lines. Only when the user names multiple stations with zero near/adjacent/distance wording may you pass transitMaxMeters=1500 for the wider multi-station scope, and you must describe it as 1,500m; if you send no distance intent the server searches within 1000m. Shuttle/shuttle van/รถรับส่ง/รถตู้ is a facility label only; pass facilities=['shuttle'] if required, but do not use shuttle to relax transit distance, and mention that service availability should be confirmed again. If the tool returns invalid_tool_call, retry with corrected arguments and do not show room results from that failed call. For 'more options' or requirement changes like budget/pet/facilities, reuse the same scope and pass excludePropertyIds with all ids already shown where relevant. If no results remain in that scope, ask before expanding. Facilities must be concrete required amenities/building facilities; send canonical English facility values, translate non-English words before calling, and do not pass vibe words as facilities. Option numbers always refer to the latest successful result list that displayed rooms; zero-result searches do not create options. Before answering about option N, verify the latest displayed room list contains option N; if it has fewer rooms, ask which previous room/list the user means instead of guessing from an older list. Do NOT call this for a follow-up about a room already shown (deposit, wifi, facilities, map, how to book, move-in date) — use get_property_details with that room's id instead, and never re-search a room the user already picked.

search_properties