AutoMotion

Reserve a rental vehicle at a rental location. Call after find_locations once the user has chosen a rental location and provided pickup/return dates and their contact details. This is a single-shot reservation: it does not need a session_id. The reservation holds as a guest with no payment (pay at pickup); a confirmation email with a cancel link is sent to the customer. Do NOT fabricate customer information. Collect every required field from the user first. When to use: - User has chosen a rental location from find_locations and wants to reserve a vehicle - You have pickup and return dates and the user's name, email, and phone When NOT to use: - Before calling find_locations — you need a valid account_id first - Without explicit user confirmation of the dates, vehicle class, and contact details

book_rental

Book a service appointment at a location. Works on its own, but a preceding get_availability call for the same account_id and vehicle already starts preparing the booking in the background, so this call finishes fast when it follows one. Booking drives the dealer's real scheduling flow, which can take a minute or two. Retry on one status and no other. Status "pending" means nothing has been sent to the dealer yet, so call book_appointment again with the same details after the wait the result names. Status "submitted" means the request left the browser and may already be a real appointment, so do NOT call again and do not tell the user it is definitely booked. Do NOT fabricate customer or vehicle information. Collect all required fields from the user first. A confirmed booking sends a confirmation email to the customer's email address. A submitted one may not, because the booking itself is not certain. You already asked the customer for their vehicle make, model and year when you called get_availability (AMS-1071): send the same values here, gated the same way. Send vehicle whenever you have it, EXCEPT when the location's booking.form_type from find_locations is CDK, REYNOLDS or GOODYEAR -- those three reject any named vehicle outright, so omit vehicle on this call for those even though you are holding the customer's answer. Several other platforms (Caliber, Monro, Tires Plus, Wheel Works, Firestone and more) require vehicle to book at all, so withholding it there fails the booking instead of protecting it. When to use: - The user has confirmed a specific slot (from get_availability) and wants to book it - You have collected customer name, email, and phone When NOT to use: - Before the user has confirmed a specific slot and provided contact details

book_appointment

✅ PRIMARY TOOL for all location searches. Handles brand + location combinations automatically. What this returns: Service locations matching your criteria, sorted by distance when location provided. PARAMETERS: - brand_name (optional): Human-readable brand like "Honda", "Tire and Wheel", "Glass Repair", "Rent a Car", "General Repair", "Collision Repair" - latitude/longitude (optional): Search center coordinates - service (optional): The service the user asked for, like "Oil Change", spelled as the services list spells it - brand_name and coordinates are both optional, but provide at least one SEARCH MODES (automatically determined): 1. Brand + Location → Up to 20 nearest locations for that brand (most common) 2. Location only → Up to 20 nearest locations of all brands 3. Location + service → Up to 20 nearest locations whose business type offers that service 4. Brand only → Up to 20 locations for that brand nationwide, not necessarily the closest ones (rarely needed; ask for the user's location instead when you can) The service parameter narrows mode 2 into mode 3. It is ignored when brand_name is given, because a brand already names what the location does. LOCATION HANDLING: - If user specifies a location (city, address, "near X"), geocode it to lat/lng - If user says "near me" or doesn't specify location, USE THE USER'S KNOWN COORDINATES - Always default to user's current/known location when available EXAMPLES: - "Find Honda locations near me" → brand_name="Honda" + user's coordinates - "Tire shop in Brooklyn" → brand_name="Tire and Wheel" + Brooklyn coordinates - "Glass repair Charlottesville" → brand_name="Glass Repair" + Charlottesville coordinates - "Auto repair shop in Tulsa" → brand_name="General Repair" + Tulsa coordinates - "Body shop in Reno" → brand_name="Collision Repair" + Reno coordinates - "Locations near me" → just coordinates (no brand) - "Who can do an oil change near me?" → coordinates + service="Oil Change" - "All Toyota locations" → brand_name="Toyota" only (nationwide, capped at 20; ask where the user is instead when you can) SPECIALTY SERVICES (use brand_name): - Tires/wheels → brand_name="Tire and Wheel" - Auto glass → brand_name="Glass Repair" - Car rental → brand_name="Rent a Car" - General repair → brand_name="General Repair" - Collision/body shop → brand_name="Collision Repair" UNIVERSAL SERVICES (no brand needed): - Oil change, brake service, car maintenance → location, plus service="Oil Change" or the matching name - Sending the service narrows the results to business types that offer it. Location alone returns every nearby location that takes general service work, which is the old behaviour and still valid. Each result includes: - booking.next_tool: The tool to call next for this location. Call that tool, do not infer one from the brand name - booking.flow: appointment, rental, quote_form, or none - booking.agent_ready: this account's own agent-booking setting. Do not route on it. booking.next_tool is the routing answer and already accounts for it, so a location reporting false can still name a scraper tool - business_category: Type of business - services: Array of services offered - booking.map_url: URL to book a service appointment online (rendered as the "Book Online" link). Use this one for any link shown to the user. - booking.schedule_service_url: the raw entry URL get_availability/book_appointment drive directly. Never print this as a clickable link when booking.map_url is present; the rendered list falls back to it only when booking.map_url is null. Returns: Service locations as a formatted list with names, addresses, and booking links. locations is capped at 20 even when more exist; total_count in the structured response says how many there actually were. If total_count is higher than the number of locations returned, tell the user the list is partial and offer to narrow by location. The overflow only happens on a brand-only nationwide search, where service is already ignored, so service cannot narrow it.

find_locations

Get available appointment slots at a service location. Call after find_locations once the user has chosen a location. Read-only: this shows availability and reserves nothing. Safe to call freely, including to compare multiple locations. Once a location is chosen, this call already starts preparing the booking in the background, so a book_appointment call for the same account_id and vehicle finishes fast instead of starting cold. Pass the same vehicle to book_appointment that you pass here. One turn happens before this tool is ever called. ASK WHAT DAY AND TIME THE CUSTOMER WANTS FIRST, before anything else -- day and time together, as the one exception to the one-thing-per-turn rule below. If they name a day, a time, or both, pass them as requested_date/requested_time. A ready response then names the matching or nearest slot directly (see those fields' own descriptions) instead of making the customer pick one out of a list. Once that answer is in hand, ASK FOR THE CUSTOMER'S FIRST NAME IN THE SAME MESSAGE THAT STARTS THIS CALL, before any result exists. That message is what starts the call; the day/time turn above is the only thing that comes before it. The four contact fields are fixed and ordered and the first is always first_name, so nothing in the response is needed to ask it. This read can take a minute or more, and that minute is what the question is for. Waiting for the result before asking spends the wait and then starts the questions, which is the one outcome this design exists to avoid. Also ask for the customer's vehicle make, model and year in that same opening message (AMS-1071), joining the day/time and first_name asks already there. Ask every time, regardless of what service they want: holding the value costs nothing, and several platforms require it to book at all. Whether that value belongs on THIS call is a separate question from whether you asked for it. Send vehicle here whenever you have it, EXCEPT when the location's booking.form_type from find_locations is CDK, REYNOLDS or GOODYEAR -- those three reject any named vehicle outright, supported or not, so omit vehicle on this call for those and hold the value for later instead. Every other form_type either requires vehicle to book or ignores it harmlessly, so sending it is always safe there. While the response says pending, the dealer's scheduling is still loading and the rest of that wait is yours to fill. From last_name onward, ask the customer for EXACTLY ONE thing per turn, the field named in next_question, and never put two questions in one message. first_name is not sourced from next_question: it was already asked, eagerly, in the message that started the call, before any response existed to name it. After each customer reply, call get_availability again with that field added to collected. While next_question is present, do not wait on a timer: the customer's answer is what triggers the next call. Keep going until you hold first_name, last_name, email and phone, then choose a slot from the ready response and call book_appointment. Those are book_appointment's own field names, so collect the first and last name as separate values even if you ask for the full name in one breath. Once you hold all four and the response is still pending there is no question left to ask, so that response carries retry_after_seconds instead of next_question. Call again on the customer's next message or after that many seconds, whichever comes first. That is the only pending response that names a delay. When to use: - User has selected a location from find_locations results and wants to book an appointment - You have the account_id and (optionally) the user's vehicle When NOT to use: - Before calling find_locations — you need a valid account_id first - To check hours or pricing — this tool only returns appointment slot availability

get_availability

List the rental vehicle classes available at a rental location, with prices. Call after find_locations once the user has chosen a rental location. Read-only: this reserves nothing and books nothing, so it is safe to repeat. Not free, though: every call drives a live headless-browser scrape and the scraper runs a single worker, so calls queue behind each other and behind any booking in progress. Compare two or three locations at most, one at a time, and prefer the locations find_locations already ranked over sweeping the list. Call this when the user wants to choose a vehicle class or see prices. book_rental takes vehicle_class as an optional argument and picks the first available class when it is omitted, so this call is not a prerequisite for booking. When to use: - The user picked a car rental location and wants to know what vehicles or prices are available - You need a valid vehicle_class value before calling book_rental When NOT to use: - For service or repair appointments, use get_availability instead. This tool serves rental brands only - Before find_locations, since you need a valid account_id first

get_rental_availability

Use this when: User wants to book an appointment or get contact details for a specific location from search results. ⚠️ CRITICAL LIMITATIONS: This tool returns ONLY contact information and booking URL. It does NOT provide: - Appointment availability or scheduling details - Service center hours or wait times - Pricing, service quality, or reviews - Operational details about this specific location - Any information beyond basic contact details DO NOT make recommendations about: - Best time to book appointments - Service quality or reliability - Location practices or upselling patterns - Wait times or service speed What this ACTUALLY returns: - Booking URL (map_url, for user to schedule directly; show this one, not booking_url) - Email and address - List of brands/products the location carries When to use: - ✅ User needs booking URL or contact info for a specific location - ✅ User asks "How do I contact this location?" When NOT to use: - ❌ User asks about hours, availability, pricing, wait times → Tell them to use booking URL or contact via email - ❌ Searching for locations → Use find_locations instead After calling this tool: Provide ONLY the contact info returned, and offer only the fields that came back. map_url, booking_url and the contact email are all nullable. Show the user map_url for scheduling questions, falling back to booking_url only when map_url is null; never show booking_url when map_url is present. Fall back to the email when neither URL is present, and when nothing is present say the location returned no way to reach it rather than inventing a link or an address.

get_booking_details

Use this when: User asks "what brands do you have?", "what car companies are available?", or wants to see all options before searching for locations. What this does: Returns complete list of car manufacturers AND service providers in the network. IMPORTANT: "Brands" is overloaded - includes TWO categories: 1. Car Manufacturers: Honda, Toyota, BMW, Ford, etc. (brand-specific locations) 2. Service Providers: Tire and Wheel, Glass Repair, Rent a Car, General Repair, Collision Repair, etc. (work with ANY vehicle) When to use: - "What car brands do you support?" - "Do you have Honda locations?" - "What services are available?" - "Can I find glass repair shops?" When NOT to use: - User just wants nearby locations without caring about brand → Skip this, go straight to find_locations - General car questions like "What's the best car to buy?" or "Tell me about Honda reliability" → Use web search instead - Questions about car prices or features → Use web search instead Returns: Categorized list of car manufacturers and service providers with IDs and logos. Use this info to answer questions about brand availability.

list_brands

Submit a quote or appointment-request lead to a location that uses a lead form (e.g. an Allstate agent). Call after find_locations once the user has chosen a location and provided their contact details. This sends a request, never a booking. No appointment time is held and no time is reserved: the business receives the lead and contacts the customer to arrange one. Tell the user that nothing is scheduled yet, and use get_availability or book_appointment when the location supports real scheduling. This is a single-shot lead submission: it does not need a session_id and returns no confirmation number. Submitting emails the request to the agent and CANNOT be un-sent, so confirm the details with the user first. Do NOT fabricate customer information. Collect every required field from the user first. When to use: - User has chosen a lead-form location from find_locations and wants to request a quote or appointment - You have the user's name, email, and phone When NOT to use: - Before calling find_locations — you need a valid account_id first - Without explicit user confirmation of their contact details and any requested contact time

submit_quote