1. Resolve the store and work
find_stores → list_services → find_vehicles → search_tires → get_appointment_times
Ask which store and what the person needs. Use real vehicle and fitment choices, current service options and store-local times. Explain installed versus tire-only prices, unknown or stale stock, and any order-in arrival limits.
2. Prepare, read back and get approval
prepare_appointment → confirm_appointment
Preparation returns a summary and confirmation token; it does not reserve or submit the appointment. Read or show the exact summary and pay-at-store terms, get the person’s explicit approval, then confirm that token. Never manufacture approval. No card payment or repair authorization is collected here.
3. Check the actual outcome
get_appointment
Keep the returned booking reference private and check status. Saved, queued, retrying, review or rejected requests are not confirmed appointments. Only the verified appropriate revision confirms its appointment. A callback is staff follow-up, not an appointment.
4. Reschedule or cancel the same booking
get_reschedule_times → prepare_reschedule → prepare_cancellation → confirm_appointment → get_appointment
Use the existing booking reference, prepare the change and obtain explicit approval of its summary before confirming. Keep the last confirmed appointment distinct from a pending change. Cancellation is complete only when its actual status says so.
Guest discovery and booking do not require a staff API key or customer account. Keep confirmation tokens, the booking reference and private receipt links out of public content and logs. A booking reference grants access to that booking; it does not prove customer-account ownership.
llms.txt is optional guidance for readers, not an MCP registration standard or a guarantee of Google, ChatGPT or other assistant inclusion, recommendations or ranking.
Read llms.txt