Restaurant Booking MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_MAPS_API_KEY | Yes | Your Google Maps API key with Places API enabled |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_restaurantsB | Search for restaurants based on location, cuisine types, mood, and event type. Returns top 3 AI-recommended restaurants within 3km radius. You can also search for specific food types using keywords. |
| get_restaurant_detailsB | Get detailed information about a specific restaurant including reviews, photos, and opening hours |
| get_booking_instructionsC | Get instructions on how to make a reservation at a specific restaurant |
| check_availabilityC | Check availability for a restaurant reservation (mock implementation) |
| make_reservationC | Attempt to make a restaurant reservation (mock implementation) |
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 5 tools
Each tool has a clearly distinct purpose: check_availability verifies reservation slots, get_booking_instructions provides procedural guidance, get_restaurant_details offers venue information, make_reservation books a table, and search_restaurants finds restaurants. There is no overlap or ambiguity between these functions.
All tool names follow a consistent verb_noun pattern with snake_case: check_availability, get_booking_instructions, get_restaurant_details, make_reservation, and search_restaurants. The naming is predictable and uniform throughout.
With 5 tools, the server is well-scoped for restaurant booking, covering key operations like search, details, availability, reservation, and instructions. Each tool earns its place without being too sparse or bloated.
The tool set covers core workflows: search, get details, check availability, make reservation, and get instructions. A minor gap exists in update/cancel reservation operations, but agents can work around this for basic booking tasks.