ijburgeats-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IJBURGEATS_CONFIG | No | Set IJBURGEATS_CONFIG to use a different path for the configuration file. Default is ~/.config/ijburgeats/config.toml. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_restaurantsA | List the restaurants on IJburg Eats with a short description and their menu categories. Restaurant names are not available as text; identify them by description and categories. |
| get_menuA | Menu of one restaurant (store_id from list_restaurants), optionally one category only. Products with has_choices=true need get_product_options before add_to_cart. |
| search_menuA | Search all restaurants' products by name, description or category (case-insensitive). |
| get_product_optionsA | Choices for a product. Each addon group needs exactly one option id; toppings are optional extras (respect max_in_group when set). Prices are surcharges per item. |
| add_to_cartB | Add a product to the cart and return the updated cart. Nothing is ordered yet. |
| view_cartA | Current cart: items (with row_id), delivery cost, total and minimum-order status. |
| update_cart_itemA | Change the quantity of a cart line (row_id from view_cart); 0 removes it. |
| clear_cartB | Remove everything from the cart. |
| get_order_historyA | Past orders of the logged-in account (newest first): order_id, time, total, status and items with the choices made. "Transactie kosten" is the old online-payment fee, not food. |
| reorderA | Add the items of a past order (order_id from get_order_history) to the cart, matched by name against the current menu. Reports items no longer on the menu (skipped) and items whose required choice could not be matched (needs_choice: ask the user, then use add_to_cart with the matched ids plus their pick). Nothing is ordered; continue with review_order. |
| get_delivery_timesA | Available delivery slots for a day (YYYY-MM-DD, default today). Pass a slot's value as delivery_time to review_order / place_order; "ASAP" means as soon as possible. |
| review_orderA | Prepare checkout without ordering: sets the delivery time and returns items, address, payment method and total_to_pay. Show this to the user and get explicit confirmation before calling place_order. payment is a value from payment_options (e.g. MSP_Ideal, WINKEL_Cash). |
| place_orderA | PLACE A REAL ORDER that costs money. Only call after the user explicitly confirmed the review_order result. expected_total must equal review_order's total_to_pay; the order is refused if the total changed. For iDEAL/card, give the user the returned payment_url to pay in their browser; the order is only final once paid. note is an optional message for the restaurant/driver. |
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 13 tools
Each tool targets a clearly distinct step in the food-ordering flow: browsing (list_restaurants/get_menu/search_menu), cart management (view/add/update/clear), checkout (review_order/place_order), and history/reorder. The boundary between reorder and add_to_cart is also clearly described.
Tool names are uniformly snake_case and almost all follow a verb_noun pattern (view_cart, add_to_cart, place_order, etc.). The only deviation is reorder, which is a bare verb rather than a verb_noun phrase, but it remains understandable.
With 13 tools, the set is well-scoped for an online food-ordering assistant. It covers discovery, cart operations, checkout, and past-order workflows without excessive granularity.
The core order lifecycle is covered: browse restaurants/menus, manage cart, choose delivery time, review, and place an order. Minor gaps exist around listing payment options explicitly, cancelling or tracking an active order, and managing user/address details, but agents can mostly work around them.