mcp-opentable
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| opentable_statusA | Check if the user is logged in to OpenTable. Returns login status and instructions if not authenticated. Call this before any other OpenTable operations. |
| opentable_loginA | Get the OpenTable login URL and instructions for the user to authenticate. Use this when opentable_status returns not logged in. |
| opentable_logoutA | Clear the stored OpenTable session cookies. Use this to log out or reset the authentication state. |
| opentable_searchB | Search for restaurants on OpenTable by location, cuisine, party size, date, and time. |
| opentable_get_restaurantB | Get detailed information about a specific restaurant including description, address, hours, and features. |
| opentable_check_availabilityA | Check available reservation time slots for a restaurant on a specific date and party size. |
| opentable_make_reservationA | Book a restaurant reservation on OpenTable. Set confirm=false to preview before booking, confirm=true to actually book. Requires the user to be logged in. |
| opentable_get_reservationsA | List all upcoming reservations for the logged-in user. Requires authentication. |
| opentable_cancel_reservationA | Cancel an existing reservation. Set confirm=false to preview, confirm=true to actually cancel. This action cannot be undone. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a distinct resource or action: authentication, search, restaurant details, availability, and reservation lifecycle. There is no meaningful overlap between tools, and the preview/confirm parameters within make/cancel reservation do not create ambiguity.
All tools share the consistent 'opentable_' prefix and mostly follow a verb_noun pattern such as search, get_restaurant, check_availability, and make_reservation. Minor deviations include opentable_status (noun instead of get_status) and opentable_login/logout (verbs without an object), but the pattern remains predictable.
Nine tools is well-suited for an OpenTable server covering authentication, restaurant discovery, availability checking, and reservation management. Each tool has a clear purpose and the count feels appropriately scoped.
The tool surface covers the core user journey: authenticate, search restaurants, view details, check availability, make reservations, list reservations, and cancel. The main gap is the lack of an update/modify reservation tool, though agents can work around it by canceling and rebooking.