Ordinary form retry
Uncertainty can become a duplicate
- 1Send booking
- 2Success response disappears
- 3Send the whole form again
Possible result: 2 bookings
Fictional Kyoto booking · WebMCP demo
Did my hotel booking go through?
The booking reached this device, but the success response disappeared. A safe retry finds the first result instead of making a second booking.
予約は端末に届いたのに、成功画面だけ消えた——そんな再送を、二重予約にしないデモです。
Current status
OnlineEMPTY
No simulated booking has been prepared on this device.
No booking result yet.
- Attempts
- 0
- Bookings
- 0
- Effect starts
- 0
03 · What WebMCP changes
The assistant can check before it retries
WebMCP is a small, named contract between this page and an assistant. It exposes four safe actions, so the assistant can read the booking state instead of guessing from pixels or sending the form again.
WebMCP safe retry
Named tools recover the first result
- 1Check the same UUIDv5
- 2Read the stored status
- 3Return the same confirmation
Verified result: 2 attempts → 1 booking
The useful part is simple: the assistant gets a safer question to ask—“Does this exact booking already exist?”—before anything is sent again.
04 · Agent boundary
Four safe WebMCP tools
Checking browser support…
check_existing_hotel_bookingRead whether this booking already exists.
prepare_hotel_bookingValidate details and create a short-lived preparation.
get_hotel_booking_statusRecover the same status and confirmation after a lost response.
preview_hotel_cancellationRead the deadline and possible fee without changing anything.
No WebMCP tool can confirm, pay for, or cancel a booking.
Public release evidence: 194 executable Node.js tests pass.
05 · Honest integration record
Connected does not mean verified
Installation, sign-in, deployment, and live execution are recorded separately.
Loading the machine-readable service record…