add_to_cart
ChatGPTAdd a service to cart and get a checkout URL. Use data from prior search/details [ACTION_DATA]. PARKING: listing.listingId, listing.serviceType="PARKING", item.checkin, item.checkout, item.parkingTypeId CARWASH: listing.listingId, listing.serviceType="CARWASH", item.passType, item.itemId (pass-level ID from car_wash_details) REPAIR: listing.listingId (shop ID), listing.serviceType="RepairAndMaintenance", item.itemId (service-level ID from auto_repair_details), item.startDateTime For PARKING only, the server auto-corrects reversed and past dates and says so in the result — tell the user the corrected dates. Returns a checkout URL — show it as a link. Errors are returned with an actionable message describing what went wrong and whether retrying will help.
auto_repair_details
ChatGPTGet details for a specific auto repair shop by listing ID. Use the "id" from a prior auto_repair_search [ACTION_DATA] — do NOT search again. Show the display text verbatim. [ACTION_DATA] contains servicePrices with service-level IDs. A service with servicePrice 0 is "Priced at shop": the shop quotes it and it is paid after the service. To book, use the bookAction of the ONE service the user chose, from servicePrices[].prices[] — it carries that service's itemId (and, for walk-in shops, a suggested startDateTime). The listing-level bookAction names no service: never call add_to_cart with it. For walk-in shops startDateTime is an estimated visit time, not a strict appointment. Appointment-required shops are also booked online: ask the user for the appointment date and time (within the shop hours), then call add_to_cart with it as item.startDateTime. Shops whose booking type is unknown, and appointment shops that publish no hours (onlineBookingSupported=false), cannot be booked online — advise the user to call the shop.
auto_repair_search
ChatGPTSearch for auto repair and maintenance shops near a location. Returns up to 12 shops. Requires lat/lon — resolve location names, city names, and addresses to coordinates before calling. For cities and addresses, use your own knowledge to estimate coordinates. RESULTS ARE SHOWN AS AN INTERACTIVE WIDGET: results render automatically as a rich card/widget. Do NOT repeat, list, or reformat the results as text, tables, or bullet lists — the widget displays them. Reply in one or two plain sentences using the summary line returned with the results (it names the lowest-priced and closest options); never as a list or table. The [ACTION_DATA] block holds shop IDs for follow-up calls only; use them for auto_repair_details — do NOT search again. To book: first call auto_repair_details to get service info, then call add_to_cart.
car_wash_details
ChatGPTGet details for a specific car wash location by listing ID. Use the "id" from a prior car_wash_search [ACTION_DATA] — do NOT search again. Show the display text verbatim. [ACTION_DATA] contains passTypes with itemId for booking. To book: call add_to_cart with listingId, serviceType="CARWASH", item.passType, item.itemId (from passTypes — NOT the location ID).
car_wash_search
ChatGPTSearch for car wash locations near a coordinate. Returns up to 12 listings. Requires lat/lon — resolve location names, city names, and addresses to coordinates before calling. For cities and addresses, use your own knowledge to estimate coordinates. RESULTS ARE SHOWN AS AN INTERACTIVE WIDGET: results render automatically as a rich card/widget. Do NOT repeat, list, or reformat the results as text, tables, or bullet lists — the widget displays them. Reply in one or two plain sentences using the summary line returned with the results (it names the lowest-priced and closest options); never as a list or table. The [ACTION_DATA] block holds listing IDs for follow-up calls only; use them for car_wash_details — do NOT search again. To book: first call car_wash_details to get pass info, then call add_to_cart.
cruise_search
ChatGPTSearch for parking near a US cruise port. Returns nearby lots sorted by relevance. Use this tool when the user mentions a cruise, cruise port, ship departure, or port parking. PORT CODES — pass the exact 3-letter code for the port: PCV — Port Canaveral, Cape Canaveral, FL POM — Port of Miami, Miami, FL PEV — Port Everglades, Fort Lauderdale, FL GAL — Port Galveston, Galveston, TX TPM — Port of Tampa, Tampa, FL CPL — Cape Liberty Cruise Port, Bayonne, NJ LPA — Port of Los Angeles, Los Angeles, CA BAL — Port of Baltimore, Baltimore, MD SDB — Port of San Diego, San Diego, CA NOL — Port of New Orleans, New Orleans, LA MCT — Manhattan Cruise Terminal, New York City, NY LGB — Port of Long Beach, Long Beach, CA SFP — Port of San Francisco, San Francisco, CA PPB — Port of Palm Beach, Riviera Beach, FL CLB — Carnival Cruise Terminal, Long Beach, CA SEA — Port of Seattle, Seattle, WA PCB — Boston Cruise Port, Boston, MA CHS — Port of Charleston, Charleston, SC DATES: Cruise parking uses departure (checkin) and return (checkout) dates. - Departure = when user leaves their car / boards the ship - Return = when user comes back / picks up the car - Pass checkinRaw and checkoutRaw as the date phrases only (e.g. "may 4") — never the whole message - Default if no dates given: tomorrow for 7 days - "sailing May 4, returning May 9" → checkin="2026-05-04 10:00:00", checkinRaw="may 4", checkout="2026-05-09 18:00:00", checkoutRaw="may 9" - "cruising next week for 7 nights" → checkin = next Monday 10:00, checkout = following Monday 18:00 BOOKING FLOW: 1. cruise_search → get listings 2. parking_details → get full details, shuttle info, amenities for a specific listing 3. add_to_cart → book with listingId, serviceType="PARKING", checkin, checkout, parkingTypeId RESULTS ARE SHOWN AS AN INTERACTIVE WIDGET: results render automatically as a rich card/widget. Do NOT repeat, list, or reformat the results as text, tables, or bullet lists — the widget displays them. Reply in one or two plain sentences using the summary line returned with the results (it names the lowest-priced and closest options); never as a list or table. The [ACTION_DATA] block holds listing IDs for follow-up calls only; use them for parking_details or add_to_cart.
ev_details
ChatGPTGet details for a specific EV charging station by listing ID. Use the "id" from a prior ev_search [ACTION_DATA] — do NOT search again. Show the display text verbatim. EV stations are NOT bookable on Way — do NOT call add_to_cart.
ev_search
ChatGPTSearch for EV charging stations near a location. Returns up to 12 stations. Requires lat/lon — resolve location names, city names, and addresses to coordinates before calling. For cities and addresses, use your own knowledge to estimate coordinates. RESULTS ARE SHOWN AS AN INTERACTIVE WIDGET: results render automatically as a rich card/widget. Do NOT repeat, list, or reformat the results as text, tables, or bullet lists — the widget displays them. Reply in one or two plain sentences using the summary line returned with the results (it names the lowest-priced and closest options); never as a list or table. The [ACTION_DATA] block holds station IDs for follow-up calls only; use them for ev_details — do NOT search again. EV stations are NOT bookable on Way.
gas_details
ChatGPTGet details for a specific gas station by listing ID. Use the "id" from a prior gas_search [ACTION_DATA] — do NOT search again. Show the display text verbatim. Gas stations are NOT bookable on Way — do NOT call add_to_cart.
gas_search
ChatGPTSearch for gas stations near a location with fuel prices. Returns up to 12 stations. Requires lat/lon — resolve location names, city names, and addresses to coordinates before calling. For cities and addresses, use your own knowledge to estimate coordinates. RESULTS ARE SHOWN AS AN INTERACTIVE WIDGET: results render automatically as a rich card/widget. Do NOT repeat, list, or reformat the results as text, tables, or bullet lists — the widget displays them. Reply in one or two plain sentences using the summary line returned with the results (it names the lowest-priced and closest options); never as a list or table. The [ACTION_DATA] block holds station IDs for follow-up calls only; use them for gas_details — do NOT search again. Gas stations are NOT bookable on Way.
parking_details
ChatGPTGet details for a specific parking location by listing ID. Use the "id" from a prior parking_search [ACTION_DATA] — do NOT search again. Show the display text verbatim. [ACTION_DATA] contains IDs for booking. To book: call add_to_cart with listingId, serviceType="PARKING", checkin, checkout, parkingTypeId from [ACTION_DATA].
parking_event_listings
ChatGPTGet parking lots for a specific event at a venue. This is Step 3 of event parking. Prerequisites: a venueId and eventId from parking_search with parkingSearchMode="event" (or parking_event_search for the same venue). Flow recap: 1. parking_search with parkingSearchMode="event" → venueId + upcoming events; each event has startsAt / endsAt and a pickAction holding this tool's exact params 2. User picks an event 3. Call THIS tool with that event's pickAction params: venueId, eventId, and its startsAt / endsAt as checkin / checkout checkin/checkout are the event's own start and end times. Response format is the same as parking_search — pre-formatted listings with booking actions. To book: call add_to_cart with listingId, serviceType="PARKING", checkin, checkout, parkingTypeId from [ACTION_DATA].
parking_event_search
ChatGPTGet the upcoming events at a venue you already have a venueId for. Not the first step: parking_search with parkingSearchMode="event" finds the venue near the coordinates and returns its venueId with its upcoming events in one call. Use THIS tool only to list that venue's events for a different date range (filters.dateFrom / dateTo). Other parking searches (hourly, daily, airport) do not return venues. Flow: 1. parking_search with parkingSearchMode="event" → venueId + events, each with a pickAction 2. Show the events and ask the user to pick one 3. Call the picked event's pickAction (parking_event_listings) → parking lots for that event venueId is a number (e.g. 699609), from that event-mode result (structuredContent.venueId or ACTION_DATA).
parking_search
ChatGPTSearch for parking near a location. Returns up to 12 listings. Requires lat/lon — resolve location names, city names, addresses, and airport codes to coordinates before calling. For cities and addresses, use your own knowledge to estimate coordinates. US airport coordinates (use these EXACT values when user mentions an airport): ATL 33.6361631,-84.4293751 | LAX 33.942153,-118.4036052 | ORD 41.9802588,-87.9089858 DFW 32.8990434,-97.0335765 | DEN 39.8563497,-104.6763991 | JFK 40.6446245,-73.7797035 SFO 37.6160605,-122.392304 | SEA 47.4417712,-122.2992778 | LAS 36.0830907,-115.1482238 MCO 28.431137,-81.3200532 | EWR 40.6895314,-74.1744624 | MIA 25.7951459,-80.2795092 CLT 35.2202031,-80.9438607 | PHX 33.435249,-112.010124 | IAH 29.9869809,-95.3410252 BOS 42.3656154,-71.0095581 | MSP 44.882625,-93.2107720 | FLL 26.0719802,-80.1500976 DTW 42.2257396,-83.3474482 | PHL 39.8729797,-75.2436987 | LGA 40.7733035,-73.871781 BWI 39.1775921,-76.6683889 | SLC 40.7909957,-111.9767932 | DCA 38.8536245,-77.0440674 IAD 38.9523404,-77.4586344 | SAN 32.7332017,-117.1896607 | MDW 41.7867759,-87.7521884 TPA 27.9768646,-82.5302804 | HOU 29.6459141,-95.2768951 | PDX 45.5882665,-122.5943981 BNA 36.124453,-86.6781078 | AUS 30.1989309,-97.678815 | STL 38.7499403,-90.374819 DAL 32.8447943,-96.8494553 | RDU 35.8800790,-78.7879963 | MCI 39.2945903,-94.7074081 SNA 33.674687,-117.8692422 | OAK 37.7126998,-122.2140441 | SJC 37.364033,-121.928885 IND 39.7202761,-86.293926 | PIT 40.4928542,-80.2372941 | SAT 29.5280092,-98.4714994 RSW 26.5337051,-81.7553083 | HNL 21.3186185,-157.9254381 | SMF 38.6956336,-121.5911639 ABQ 35.0405314,-106.6097996 | BUR 34.1983122,-118.3574036 | ONT 34.0559976,-117.5980922 CLE 41.4057985,-81.8538669 | JAX 30.4914174,-81.6835683 | MEM 35.0443357,-89.9766187 BUF 42.9412697,-78.7303413 | TUL 36.1961679,-95.8867789 | MKE 42.9438861,-87.9007655 CVG 39.051351,-84.6671453 | PBI 26.6857475,-80.0928165 | RIC 37.5046289,-77.3196762 MSY 29.9852624,-90.2572882 For any airport not listed above, use your own knowledge to estimate coordinates. DATES: Convert relative dates to "YYYY-MM-DD HH:mm:ss" AND pass just the date phrase (e.g. "tuesday", "march 24") in checkinRaw/checkoutRaw. The server uses checkinRaw/checkoutRaw to VERIFY and AUTO-CORRECT your date calculation — so even if you miscalculate, the server fixes it. checkin = DEPARTURE date (when the user leaves / drops off the car). checkout = RETURN date (when the user comes back / picks up the car). CRITICAL: Day names ALWAYS mean the NEXT upcoming occurrence. If today is Monday and user says "Tuesday", that means TOMORROW (1 day ahead, not 8 days). Never skip to next week when this week's day is still upcoming. Step-by-step: (1) Identify today's weekday and date. (2) Count forward to the NEAREST future occurrence of the target day. (3) Calculate YYYY-MM-DD. Example: If today is Monday March 24, "Tuesday" = March 25 (1 day ahead). "Thursday" = March 27 (3 days ahead). Pass checkinRaw/checkoutRaw as the date words only (e.g. "tuesday", "thursday") so the server can verify — never the whole message. "tomorrow morning" → next day 08:00:00 | "tonight" → today 18:00:00 "Tuesday to Thursday" → next Tuesday 10:00:00 to next Thursday 18:00:00 | checkinRaw="tuesday", checkoutRaw="thursday" "for 5 days" → checkin + 5 days for checkout | "a week" → checkin + 7 days "this weekend" → Saturday 08:00 to Sunday 20:00 Default times: use 10:00 for check-in, 18:00 for check-out if user doesn't specify a time. TRAVEL LANGUAGE — read carefully before assigning checkin/checkout: The FIRST date/day mentioned in a travel sentence is ALWAYS the DEPARTURE (checkin). The SECOND date/day (after "returning", "coming back", "back on", "until") is ALWAYS the RETURN (checkout). "traveling from LAX Tuesday morning returning Thursday evening" → checkin=Tuesday 08:00:00, checkout=Thursday 18:00:00 "flying out Monday, coming back Friday" → checkin=Monday 10:00:00, checkout=Friday 18:00:00 "leaving for vacation Wed, back on Sunday" → checkin=Wednesday 10:00:00, checkout=Sunday 18:00:00 "I need parking from March 5 to March …
add_to_cart
Claudecar_wash_details
Claudecar_wash_search
Claudecruise_search
Claudeev_details
Claudeev_search
Claudegas_details
Claudegas_search
Claudeparking_details
Claudeparking_event_listings
Claudeparking_event_search
Claudeparking_search
Clauderm_details
Clauderm_search
Claude