MCP operations tools
The tools behind the operations door /mcpoperations: the work a colleague does on a normal day. Find and update a reservation, correct a customer, run the floor plan, check guests in, log hours. A key with scope operations opens this door; how to connect is described in Connecting an AI agent to the MCP server. Setting up what can be booked happens behind the configuration door — see MCP configuration tools.
Why this is a door of its own
This catalogue reads the entire customer base. A booking key is handed to third parties — a voice platform, the backend of a widget on a customer's own site — and that is a different level of trust from a colleague working in the system. The scope is the only place where that difference can be held before a single right is consulted.
Nothing behind this door is public: every call without a logged-in user is refused, reads included.
Plan, apply and the confirmation
As with the configuration door, a writing act consists of ..._plan and ..._apply, each with its own right. For the heaviest acts an extra step is added: the plan issues a confirmation token that the apply requires. So you cannot move a booking or merge two customers in one motion — there is deliberately a moment in between at which somebody could have seen the plan.
That applies to the tools at levels 2 and 3 in the table: moving, changing participants, recording a payment, taking a walk-in, and merging customers or companies. Merging sits at the highest level because it cannot be undone.
The tools
| Tools | Read/write | Level | Description |
|---|---|---|---|
| search / day_overview / filter_columns | read | - | Search across everything, the day overview, and which columns you can use in a filter |
| booking_filter / booking_get | read | - | Find reservations and retrieve one reservation with all its detail |
| booking_create / booking_set_status / booking_set_remarks / booking_set_extras / booking_todo_add / booking_set_zone_preference | write | 1 | Create and update a reservation: status, remarks, extra options, a task, a zone preference |
| booking_move / booking_change_participants / booking_add_payment / booking_action | write | 2 | Move, change the number of participants, record a payment, perform an action — all with confirmation, because the price moves with them |
| customer_filter / customer_get / company_filter / company_get | read | - | Find and retrieve customers and companies |
| customer_create / customer_update / customer_set_status / customer_contact_add / company_create / company_update / company_set_status / company_contact_add / company_link_customer | write | 1 | Create and update customers and companies, add contacts, link a customer to a company |
| customer_merge / company_merge | write | 3 | Merge two duplicate records. With confirmation, and not reversible |
| floorplan_list / floorplan_tables / floorplan_occupancy | read | - | The floor plans, their tables and the occupancy |
| table_queue / table_assign / table_unassign / table_move / table_lock | read/write | 1 | Assign, release, move and block tables, and see what is still waiting |
| guestlist_get / guestlist_set_presence | read/write | 1 | The guest list and checking guests in or out |
| walkin_options / walkin_create | read/write | 2 | See what is free for a guest who simply walks in, and seat them |
| todo_list / statuscheck_list / customerstatuscheck_list / cancelrefundcheck_list | read | - | The work queue: tasks, status checks, and cancellations still needing a refund |
| call_list / chat_list / conversation_list / email_list / meet_list | read | - | What came in: phone, chat, conversations, e-mail and appointments |
| timesheet_status / work_activity_list / work_entry_list / work_entry_create / billable_list / billable_update | read/write | 1 | Time tracking: the state, the activities, logging hours, and what gets charged on |
You ask for the exact, always current list with all input fields using tools/list on the door itself. What you get back depends on your rights and on which modules the license has — without the floor plan module the table and guest list tools are simply not there.
BETA. This door is new and still being developed. Tool names, input fields and levels may change between releases without a transition period. Use the plan variant before applying anything, and do not yet build a production integration on it that is not allowed to break.
