LeasingAI

Submits a tour time once you have the full name, email, US phone number and time. Never guess any of them — but never collect them in prose either: call get_tour_availability first and let its card gather what is missing. Use this tool only to submit a time the visitor has confirmed. Whether that CONFIRMS a tour or REQUESTS one depends on the community: read `tour.status` in the result — `scheduled` is booked, `requested` means the leasing team has it and has not confirmed the time yet. Say which one happened; never announce a booking for a request.

book_tour

Cancels a booked tour. Confirm with the visitor first — this cannot be undone.

cancel_tour

Shows the communities this app can answer for as a pickable list. CALL THIS — never answer in prose, and never ask which community they mean — whenever the visitor wants to choose, pick, browse or change community, has not chosen one yet, or asks about one other than the current one. Showing the list IS how you ask them. Omit `query` to show a first page they can pick from; pass a city, ZIP or name to narrow it. When the result says it is showing only some of the communities, page only when the visitor asks to see more results — then pass `page` (2, 3, …) with the SAME query, filters and `limit`; otherwise offer to narrow the search. Narrow further with maxRent, minBedrooms, maxBedrooms, minBathrooms, amenities, unitFeatures, petsAllowed, leaseTermMonths or a moveInFrom/moveInTo window — pass only the ones the visitor actually named, since each one narrows the list and several at once often leaves nothing. Every requirement is checked against the SAME home, so a result is about one apartment rather than about a building. Rows come back as confirmed matches or as possible ones carrying what is still unconfirmed: read those caveats out, never present a possible match as a match, and never repeat a requirement back as met when the row says it is unknown. If nothing matches you may be offered a requirement to drop — offer it to the visitor and let them decide; do NOT call this again with it removed. Then call set_community with the id they choose.

choose_community

Compares two or more communities side by side on rent, floor plans, amenities, pet policy and parking — pass `fields` to compare on something else. Use it when the visitor is weighing communities against each other, instead of calling the property tools once per community. Every id must have come from choose_community; never invent one, and never compare a community you could not look up — say which one you could not reach.

compare_properties

Emails the visitor's own tour confirmation — including its confirmation code — to the address their tour was booked with. Use it when they already have a tour here and cannot produce the code, which is the state book_tour reports instead of booking a second one. The code is NEVER returned to you: read the acknowledgement back as written, then ask them to read the code out of their inbox, and only then look the tour up with get_tour. The reply is the same whether or not a tour exists, so never present it as proof that one does.

email_my_confirmation

Returns the property's floor plans narrowed to what the visitor asked for — pass bedrooms and/or bathrooms for an EXACT size ("show me the 2 bedrooms"), and maxRent for a budget. Use this instead of get_pricing_and_availability whenever a size or budget was named, rather than filtering a full list yourself. An empty result means no plan matches those filters, NOT that the community has none — say so, and offer to widen them.

get_floorplans

Returns where the current community is, plus nearby landmarks, transit and employers. Use for "where is it", commute and neighborhood questions. Call it straight away — you do not need to know which community first, and you must not ask the user which one they mean; if none has been chosen yet you get a picker back. Never web-search the address or reuse one from an earlier conversation or memory: this conversation may be about a different community than the one last discussed.

get_location

Returns the current community's rent and inventory in full: every floor plan with bedrooms, bathrooms, size, rent range, deposit and how many units are available, plus when that data was last refreshed. If the result carries availabilityNote, the unit counts could not be confirmed — say that note instead of any count. Use for any price or "what's available" question. Call it straight away — you do not need to identify the community first, and you must not ask the user which one they mean; if none has been chosen yet you get a picker back. Never quote rents from memory or an earlier conversation: rents change, and this result says when they were last refreshed. If the visitor asked for a specific size or budget, call get_floorplans instead of filtering this list yourself.

get_pricing_and_availability

Returns the current community's amenities, unit features, pet policy, parking, office hours, FAQ, application policy and neighborhood. Required for every such question. Call it straight away — you do not need to identify the community first, and you must not ask the user which one they mean; if none has been chosen yet you get a picker back. Never web-search this property and never answer from memory or an earlier conversation: this data is live.

get_property_details

Returns the current community for this conversation, with its name, address and contact details. That community is the default for every tool here, so you never need to identify it first. If the user says "this property" and you do not know which one they mean, call this instead of asking them, and never guess from memory, an earlier conversation, or a web search. If no community has been chosen yet you get a picker back instead. Only when they ask about a DIFFERENT community do you search for it and pass its `propertyId` — or pass `slug` if they gave you a leasing.ai property page URL.

get_property_overview