Table for Forty for AI assistants
An assistant can search our live rooms and read one room's facts, the way a guest reads the site. Every answer leads with the all-in price: the food and beverage minimum plus the venue's tax, service and gratuity, the same number the room's page shows.
Connect
- MCP server (streamable HTTP, read-only, no key):
https://officialfoodgroup.com/api/agents/mcp. In your assistant's custom connector setting, add this address. - HTTP API: the OpenAPI document describes the same two reads.
- Discovery: the MCP server card, the AI catalog and llms.txt.
The two tools
search_rooms: live rooms by city, with neighborhood, date, guests and budget. A date adds each room's availability and its dated total.get_room: one room's prices, Key facts, description, address, photos and open dates.
What can an assistant do here?
Find live rooms and read their facts: the all-in price, capacity, notice, availability, photos and the room's page. The prices are the room page's own numbers, never a second estimate.
What does an assistant never do here?
Take a payment, book a room, hold a date or send a request. It sees only what the room pages print: no guest, booking or venue account data.
How does a guest book a room an assistant found?
The guest opens the room's link and sends the request from the page, with the search already filled in. An inquiry is a request, not a booking: the venue confirms, and a deposit holds the date.
Is the price really all in?
Yes: the food and beverage minimum plus the venue's tax, service and gratuity, as the room's page shows it. A room fee, where there is one, is named beside it. A venue that adds a surcharge on card payments says so, and it is never inside the all-in.
Does it need a key?
No. The tools are read-only and public, like the pages they read.