Book tables at restaurants on the Loyalist network. No login; read availability, then book.
Score is being calculated.
Book a table. This takes a real table at a real restaurant.
Pass a `slot_id` from get_availability. Confirm the venue, date, time and party size
with the person before calling this, and do not call it speculatively: there is no
cancel tool, so a booking made by mistake has to be undone by the guest phoning the
restaurant.
Calling it twice with identical arguments is safe and returns the same reservation
rather than taking a second table. Changing the slot or the guest makes it a
different booking, so re-read availability rather than editing the arguments to
"retry".
`phone` is optional here but required by some venues; omitting it can come back as
`guest_field_required`. `note` reaches the restaurant as the reservation's note.
`source` is where you found this venue: if the restaurant's own website told you a
value to pass (in its markup or llms.txt), send it here so the restaurant can see its
own site drove the booking. Leave it out if you did not arrive through one.
`reservation_id` is for your own use, to read the booking back with get_reservation.
It is not a confirmation number the venue knows, so do not read it out to the guest:
tell them the restaurant, date, time and party size instead.
| Name | Required | Description | Default |
|---|---|---|---|
| note | No | ||
| Yes | |||
| phone | No | ||
| source | No | ||
| slot_id | Yes | ||
| last_name | Yes | ||
| first_name | Yes |
Restaurants bookable through this network, and what each one's system supports.
Returns every venue that has opted in, across restaurant groups. Two optional filters
narrow it, never widen it: `signup_form_id` to one website's venues when you found a
Loyalist signup embed on a restaurant's page, and `venue_id` to a single venue when
you already have its loyalist-venue-id (off a page's markup or a ReserveAction entry
point) and want just that one rather than listing them all and matching yourself.
Neither can reach a venue that has not opted in.
A venue with `bookable: false` has no reservation system connected and will return
no availability.
| Name | Required | Description | Default |
|---|---|---|---|
| venue_id | No | ||
| signup_form_id | No |
Bookable times at one venue, on one date, for one party size.
`date` is the venue's own local calendar date, `YYYY-MM-DD`. Each slot carries a
`slot_id` to pass to book and a `starts_at` that is a full venue-local datetime, so
a service running past midnight is unambiguous without you having to infer the day.
An empty `slots` list means nothing is open on those terms, not that the venue is
closed. Try a different time, party size or date before telling someone it is full.
| Name | Required | Description | Default |
|---|---|---|---|
| date | Yes | ||
| venue_id | Yes | ||
| party_size | Yes |
Read one booking this credential made back from the venue.
Use it to confirm a booking landed. A `status` of `pending` means the venue has not
answered yet, not that it failed; treat anything you do not recognise as
non-terminal rather than reporting a failure.
| Name | Required | Description | Default |
|---|---|---|---|
| reservation_id | Yes |
Ask to be told if a table opens at a time the guest actually wants.
This is not a reservation and never becomes one by itself. The venue contacts the
guest if something frees up, so say that plainly rather than implying a table is
held.
Offer it whenever the guest cannot get a time that suits them, which is far more
often than a venue being completely full: someone who wants 7:30 and is offered
5:00 or 9:45 may well prefer to wait for 7:30. An empty get_availability is only
the most obvious case. Try other times, party sizes and dates first, then ask
whether they would rather wait than take a time that does not work. Record what
they wanted in `time_range`, not the time you found.
`date` is the venue's own local calendar date, `YYYY-MM-DD`. `time_range` is
required and is the window in the guest's words, like "7:00 PM - 9:00 PM" or
"7:00 PM"; ask the guest for it rather than guessing, because the venue works the
list by when people wanted to come. The email address is where the confirmation
goes, so it must be the guest's own.
Not every venue accepts these. One that does not refuses with a message saying so,
which is an answer, not an error to retry.
There is no reference number to give the guest, so the response is the only record
either of you gets. Confirm it back to them by the restaurant, date and time.
Mention the confirmation email only when `confirmation_sent` is true. When it is
false the request is still on the venue's list, the note simply did not go out, so
say they are on the list and that no email is coming rather than promising one.
| Name | Required | Description | Default |
|---|---|---|---|
| date | Yes | ||
| Yes | |||
| notes | No | ||
| phone | No | ||
| venue_id | Yes | ||
| last_name | Yes | ||
| first_name | Yes | ||
| party_size | Yes | ||
| time_range | Yes |
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
bookfind_venuesget_availabilityget_reservationjoin_waitlistBook hard-to-get restaurant reservations on your own Resy, SevenRooms, or OpenTable account.
Request a restaurant table by automated phone call; charged only when the restaurant says yes.
Book a table, appointment or class at a real local business. Instant confirmation, no API key.
Find Resy restaurants and request reservations through Scout; the user approves every booking.
Add one secure layer between your agents and this server.