Skip to main content
Glama
chrischall

opentable-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

opentable_modify_preview

Read-only

Preview modifying an existing OpenTable reservation: provide the reservation's confirmation number, security token, and new slot details to get updated cancellation policy, CC re-hold info, and a modify token for finalizing the change.

Instructions

Preview a MODIFICATION to an existing OpenTable reservation. Takes the existing reservation's identity (restaurant_id + confirmation_number + security_token from opentable_list_reservations or the original opentable_book result) plus the NEW slot args (from a fresh opentable_find_slots call) and returns the new cancellation_policy, CC re-hold details, and a modify_token that opentable_modify consumes. Mirrors opentable_book_preview, but the /booking/details URL includes confirmationNumber + securityToken + isModify=true so OpenTable's SSR returns the modify state. dining_area_id is OPTIONAL — omitted, it's auto-resolved from the booking-details page like book_preview does. REQUIRED before opentable_modify — no shortcut path. For Listing-type restaurants the modify can't proceed (no slot picker); check opentable_get_restaurant.bookable first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesYYYY-MM-DD (the NEW date)
timeYesHH:MM (24h) — the NEW time
slot_hashYesslot_hash from opentable_find_slots for the NEW slot
party_sizeYes
experience_idNoFor Experience-mandatory slots; required when the new slot has experience_ids.
restaurant_idYes
dining_area_idNoOptional dining-area (room) id for the NEW slot. When omitted, auto-resolved to the default dining area from OpenTable's booking-details page — the same resolution opentable_book_preview uses. Pass explicitly only to pin a specific room.
experience_idsNoPass-through from find_slots.experience_ids. When non-empty, experience_id must also be set.
security_tokenYes
database_regionNoOpenTable's sharded-database region for the restaurant. Defaults to 'NA' (North America). Pass the venue's region (e.g. for UK/EU/APAC restaurants) when booking or cancelling outside North America — slot-lock, availability, and cancel route to the wrong database shard, or fail opaquely, when this is wrong. LIMITATION: not auto-derived from restaurant data (OpenTable's availability/booking responses don't surface the shard id), so non-NA bookings must set it explicitly.
reservation_tokenYesslot_availability_token from opentable_find_slots for the NEW slot
confirmation_numberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.18.2
    • addedInput schema / properties / dining_area_id / description
      Added value: +"Optional dining-area (room) id for the NEW slot. When omitted, auto-resolved to the default dining area from OpenTable's booking-details page — the same resolution opentable_book_preview uses. Pass explicitly only to pin a specific room."
    • changedInput schema / required
      Previous value: -[
-  "restaurant_id",
-  "confirmation_number",
-  "security_token",
-  "date",
-  "time",
-  "party_size",
-  "reservation_token",
-  "slot_hash",
-  "dining_area_id"
-]New value: +[
+  "restaurant_id",
+  "confirmation_number",
+  "security_token",
+  "date",
+  "time",
+  "party_size",
+  "reservation_token",
+  "slot_hash"
+]
  2. First observedv0.14.3

TDQS

A5/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond readOnlyHint=true, the description discloses that the endpoint returns cancellation_policy, CC re-hold details, and modify_token; that dining_area_id is auto-resolved when omitted; and that Listing-type restaurants cannot proceed. It also reveals the internal mechanism (isModify=true in the /booking/details URL), giving the agent useful expectations about behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but front-loaded: the first sentence states the purpose, and every subsequent sentence earns its place by covering source data, return values, a required precondition, and a failure mode. There is no filler or redundant restatement of schema descriptions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter, 8-required tool with no output schema, the description supplies the full call context: where identity and slot args come from, what the response contains, the mandatory position before opentable_modify, and the Listing-type failure condition. This is sufficient for an agent to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, and the description compensates by explaining the provenance of key parameters: restaurant_id + confirmation_number + security_token come from list/book results; reservation_token and slot_hash come from a fresh find_slots call. It clarifies optionality and auto-resolution of dining_area_id and the relationship between experience_ids and experience_id, mapping cleanly to the schema fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Preview a MODIFICATION to an existing OpenTable reservation' — a specific verb, resource, and scope. It distinguishes itself from opentable_book_preview by noting it 'Mirrors opentable_book_preview' but targets the modify state and returns a modify_token, so an agent can tell them apart.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states 'REQUIRED before opentable_modify — no shortcut path,' explicitly setting when this tool must be used. It directs the agent to source identity from opentable_list_reservations or the original opentable_book result, to pull NEW slot args from a fresh opentable_find_slots call, and it names the Listing-type exclusion with a check on opentable_get_restaurant.bookable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools