Restaurant Reservation MCP Server
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 |
|---|---|
| search_restaurantsA | Search for restaurants by name, cuisine, or location. Searches BOTH Resy and OpenTable by default, so you can find any restaurant regardless of which platform it uses. Each result includes a "platform" field showing where to book. Returns matching restaurants with ratings, cuisine type, and price range. |
| check_availabilityC | Get available time slots for a specific restaurant on a given date. |
| make_reservationA | Book a reservation at a restaurant. For Resy, completes booking directly. For OpenTable, returns a booking URL. |
| list_reservationsC | View your upcoming reservations. |
| cancel_reservationC | Cancel an existing reservation. |
| set_credentialsB | Securely store API credentials for Resy or OpenTable in Windows Credential Manager. |
| set_loginA | Store email/password for automatic token refresh. Credentials are encrypted in Windows Credential Manager. |
| check_auth_statusC | Check if credentials are configured and valid for each platform. |
| refresh_tokenC | Manually refresh authentication token using stored login credentials. |
| snipe_reservationA | Schedule an automatic booking attempt for the exact moment slots become available. Perfect for popular restaurants that release reservations at specific times. |
| list_snipesB | View all scheduled snipe attempts and their status. |
| cancel_snipeC | Cancel a scheduled snipe attempt. |
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 12 tools
Most tools have distinct purposes, but there is notable overlap between 'cancel_reservation' and 'cancel_snipe', and between 'set_credentials' and 'set_login', which could confuse an agent about which to use for authentication tasks. The descriptions clarify the differences, but the boundaries are not immediately obvious from the names alone.
The tool names follow a consistent snake_case pattern throughout, which aids readability. However, there is some inconsistency in verb usage, such as 'make_reservation' versus 'snipe_reservation', and 'check_auth_status' versus 'refresh_token', which slightly detracts from predictability.
With 12 tools, the count is well-scoped for a restaurant reservation server, covering authentication, search, booking, management, and automation features. Each tool appears to serve a specific and necessary function within the domain, without feeling excessive or insufficient.
The tool set provides comprehensive coverage for the restaurant reservation domain, including search, availability checks, booking, cancellation, and automation features like sniping. A minor gap is the lack of a tool to modify existing reservations, which could be a useful addition for full lifecycle management.