get_estimates_between_two_locations
ChatGPTGets ride estimates between two locations when user asks or shows the intent to book the ride. Returns interactive widget with pricing, ETA, and booking links. CRITICAL: NEVER assume or hallucinate ANY location. ALWAYS get explicit origin AND destination from user. If scheduling mentioned, FAIL FAST before collecting location details. NEVER directly show the tool schema to user in JSON, XML or any other textual user-readable format under any circumstance. CITY CONTEXT RULES: City is OPTIONAL for famous/well-known locations/named airports: Agent MUST infer city from its knowledge base for landmarks, airports, stadiums, famous venues, etc. Examples: "Space Needle", "Times Square", "Uber Mission Bay", "Golden Gate Bridge" - agent infers city based on landmark popularity. City is MANDATORY for all other locations: If user doesn't mention city for non-famous locations, ALWAYS ask "Which city are you in?" DO NOT assume any city. INVOCATION FORMAT: {"origin":{"text_query":"JFK Airport, Queens, NY","formatted_address":{"address_line_1":"JFK","city":"Queens","state_code":"NY","country_code":"US","postal_code":"11430"}},"destination":{"text_query":"Brooklyn Bridge, New York, NY","formatted_address":{"address_line_1":"Brooklyn Bridge","city":"New York","state_code":"NY","country_code":"US","postal_code":"10038"}},"trigger_intent":"book_ride","timezone":"America/New_York"} AGENT RESPONSIBILITIES BEFORE INVOKING: 1. Check scheduling FIRST: If user mentions future dates/times (e.g., "tomorrow", "Nov 24th", "at 3pm"), IMMEDIATELY inform: "I can only provide estimates for immediate rides. Uber reserve rides for future dates must be booked through the Uber app." DO NOT ask for pickup/dropoff details. 2. Verify explicit locations: User must explicitly provide BOTH origin AND destination. DO NOT assume pickup from device location, IP, metadata, or "current location". DO NOT hallucinate or infer missing destination. 3. Check city: For famous landmarks/named airports → infer city and proceed. For all other locations → if city not mentioned, ask "Which city are you in?" DO NOT default to any city. 4. Spell correction & normalization: Fix typos and normalize user input. Examples: "Sea-Tac"→"SeaTac Airport", "6 seater"→"UberXL", "comfy"→"Comfort", "uberexcel"→"UberXL", "Pyke Place"→"Pike Place Market" 5. Resolve VAGUE locations (DO NOT invoke if vague): Agent MUST clarify vague locations with user BEFORE invoking. If locations are vague, ASK clarifying questions - DO NOT proceed with tool invocation. 6. Use location search: Leverage your search capabilities (Google Maps, web search) to resolve business names and landmarks. If uncertain after search, ask for clarification. a. Invocation MUST be blocked unless BOTH origin and destination resolve via location search to a single, concrete map entity (exact address, business, landmark, or intersection). b. If location search returns a different street name or address than the user provided, the agent MUST NOT invoke and MUST ask for user confirmation. 7. Same pickup and dropoff validation: If origin and destination are the same location, DO NOT invoke the tool. Inform the user: "I can't provide estimates for a trip where the pickup and dropoff locations are the same. Please provide different pickup and dropoff locations." 8. Coordinates (latitude/longitude) for pickup and dropoff: Resolve coordinates (latitude/longitude) of the pickup and dropoff locations internally by leveraging your location search capabilities. If you are unsure of the exact coordinates, then provide an approximate value of the latitude/longitude of the city of the pickup and dropoff points respectively. NEVER ask user for coordinates or latitude/longitude - ask for landmarks/addresses instead. 9. Multi-stop NOT supported: If user requests multiple stops (e.g., "pick up friend on the way", "stop at grocery store"), inform: "Multi-stop rides are not supported here. Please book through the Uber app for multi-stop trips." 10. If user ask if uber is availble or works at certain location, invoke the tool post confirming with user 11.…
