Red Estelar

Submit a buyer requirement only after the buyer fills in their contact information and explicitly consents to contact from a Red Estelar network agent. Available only in the listings app for specific areas with fewer than 40 matching public listings.

submit_public_requirement

Estima el rango de precio de venta por metro cuadrado para una ubicación en Bogotá, Colombia. Usa coordenadas o address/neighborhood. Si el usuario indica una ciudad o país, envíalos; Bogotá y Colombia son los valores por defecto. property_type usa códigos como AP, CA, OF o LC y por defecto es AP.

estimate_zone_m2

Use this when the user asks for details about one public Inmobo listing returned by the interactive map. Pass the exact listing id from that result.

fetch

Compatibility-only app tool for loading one bounded coordinate-backed result page. It is not intended for direct model invocation and the map widget does not expose pagination controls.

list_listing_results

Use this for every model-driven request to search, find, browse, list, recommend, or show public properties. Always render results as an interactive map. Keep listing photos in the map widget. In your text response, show listing details and links without embedding remote images or Markdown image links. When preparing a requirement for the Red Estelar network, always ask when the buyer needs to move if they have not said. If they provide only a month, ask them to confirm the exact day; never assume the first. Pass the confirmed day as move_in_date in YYYY-MM-DD format. This date is requirement metadata and must not filter listing inventory. For an area BETWEEN four named Bogotá roads, pass all four spoken road names in boundary_roads, not as one address or guessed coordinates. Example: 'apartamentos en venta entre calles 100 y 170, carrera séptima y autopista' means boundary_roads ['calle 100','calle 170','carrera séptima','autopista norte'], property_type APARTAMENTO, operation VENTA, city Bogotá. Map a named person to agent_name, a named brokerage to broker_name, an exact listing code to reference, and a single street address or landmark to address. Never put an address in query. Map every requested city, neighborhood, property type, operation, price, area, room count, amenity, and description feature to its dedicated field. 'Cancha de squash' means amenities ['squash']; 'cocina abierta' means open_kitchen true; 'con 3 cuartos' means bedrooms 3; 'al menos 3 cuartos' means min_bedrooms 3. Do not put these requirements in query. Treat an explicit budget, amenity, and description requirement as mandatory. If no listing matches, say so; do not claim a listing has an amenity or kitchen feature without the database filter confirming it. For searches in a specific area or around an address, the map may show up to three recommended agents with matching listings. Rank active agents using the GET /agents/ranking method: matching listing count (40%), weighted lead-stage conversion (10%), lead volume (25%), and response speed (25%) over the last 30 days. Do not show an agent recommendation for a city-only search. For multiple neighborhoods, pass all of them in neighborhoods. A general request requires a city, neighborhood, address, boundary_roads, agent, brokerage, or reference. If none is provided, ask: ¿En qué ciudad o zona quieres buscar? También puedo usar tu ubicación actual. When the user explicitly asks to use current location, invoke this tool with use_current_location true; the widget will separately ask for consent. The widget has no search form; follow-up refinements come from the conversation.

render_listings