easytable-mcp
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| easytable_list_typesA | List the bookable areas/types for a restaurant (e.g. "Boka Inne", "Boka baren"). Returns each area's type id for use in the other availability tools. |
| easytable_list_datesA | List bookable dates for a restaurant area and party size. Each entry has an ISO date and whether it is available. |
| easytable_list_timesA | List available time slots for a restaurant area, date, and party size. Times are returned as HH:MM. |
| easytable_find_bookingsA | Look up a restaurant's existing bookings made with a given mobile number. Returns each booking's id (for easytable_cancel_booking) plus a summary. |
| easytable_cancel_bookingA | Cancel an existing booking. Look up the booking id first with easytable_find_bookings (it needs the mobile the booking was made with). Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). The first call only looks the booking up (a read); it cancels nothing. |
| easytable_create_bookingA | Create a restaurant booking. Reads the Cloudflare Turnstile token from your signed-in booking-widget tab (via the bridge) and submits it with the reservation — so a book.easytable.com/book/?id= tab must be open and loaded. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). The first call makes NO network call. |
| easytable_modify_bookingA | Modify an existing booking (date/time/party size/details). Like create, it reads the Turnstile token from your signed-in widget tab. Get the existing booking id from easytable_find_bookings. The change replaces the whole booking: email, comment and company are required — pass the booking's current values to keep them (ask the user if unknown), or '' to clear them; the newsletter opt-in is reset. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). The first call makes NO network call. |
| easytable_healthcheckA | Round-trips a small public book.easytable.com URL (/robots.txt) through ContextMint Bridge (your signed-in browser tab) and returns diagnostics: the bridge's role (host/peer/null), port, version, the extension link (linked / pair pending / not attached / never answered), the elapsed round-trip time, and a plain-English hint distinguishing 'bridge never came up' from 'extension not connected' from 'this browser can't serve a capability' from 'real book.easytable.com-side problem'. Read-only, no auth required. Call this when a real tool fails and you want to know which hop broke. |
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 8 tools
Each tool has a distinct action: booking CRUD (find/create/modify/cancel), availability lookups (list_types/list_dates/list_times), and diagnostics (healthcheck). The three list_* tools are related but clearly differentiated by what they enumerate (areas, dates, times), and descriptions reinforce their distinct purposes.
All tools use a consistent easytable_ namespace with a predictable verb_noun pattern (find_bookings, cancel_booking, create_booking, modify_booking, list_types, list_dates, list_times). Only healthcheck is a bare noun, a trivial deviation that doesn't break the pattern.
Eight tools is well-scoped for a restaurant-booking server, covering the booking lifecycle plus availability and a bridge diagnostic. No redundant or padding tools.
Full booking lifecycle is covered (create/read/modify/cancel) plus the availability trio needed to book. Gaps are minor: no restaurant-discovery/search tool to find a venue id, but the widget-tab workflow suggests that's handled externally.