Content
Content operations answer what a guest asks before they book. They all need the content.read capability and only read data.
| Question | Operation | MCP tool |
|---|---|---|
| Which venues can I book? | GET /venues |
list_venues |
| Where is it, what does it offer? | GET /venues/{id} |
get_venue |
| When is it open? | GET /opening-hours |
get_opening_hours |
| What’s on the menu? | GET /menus |
get_menus |
| What’s on? | GET /events/upcoming |
list_events |
| Dress code, parking, accessibility? | GET /knowledge/{topic} |
get_venue_knowledge |
Venues and brands
Section titled “Venues and brands”ListVenues returns the venues your key covers, with their address and time zone. GetVenue adds the description, brand and the booking types guests can book online; call it before booking to learn which booking types a venue offers. GetBrand returns a brand that has at least one venue your key can use. Over MCP, the brand name is part of get_venue.
Opening hours and menus come from the knowledge base
Section titled “Opening hours and menus come from the knowledge base”Opening hours, special one-off dates, happy hours, kitchen hours and menus come from the venue’s knowledge base, the same published documents the venue’s own agents read. Availability follows the venue’s booking hours, which are set separately. The two can differ: a bar open until 02:00 may take its last booking at 22:30. Use Check availability to find bookable times, and opening hours to answer “when are you open?”.
A menu or document the venue hasn’t published answers 404 knowledge-not-found (or null for a missing menu). If the knowledge base is briefly unreachable the answer is 503 service-unavailable.
Knowledge topics
Section titled “Knowledge topics”GetVenueKnowledge returns one published document by topic: venue-details, faq, opening-hours, happy-hours, food-menu, drinks-menu, special-hours, kitchen-hours or compendium. Questions such as dress code, parking or accessibility are usually answered in faq or venue-details.
Events
Section titled “Events”ListUpcomingEvents lists events with their dates between from and to (venue-local yyyy-MM-dd; by default today to 30 days ahead, at most 92 days), with the seats left on each date. ListEvents (events without dates) and ListEventInstances (every date, ungrouped) remain on REST; MCP has only list_events.
Features
Section titled “Features”Some operations depend on what the venue group’s deployment includes. Knowledge content (GetOpeningHours, GetMenus, GetVenueKnowledge) needs the knowledge base, and ListUpcomingEvents needs events. On a deployment without them those operations answer 404 not-found, and the MCP tools don’t appear.