EatWithMe

Requires the administration or products full access permission in the restaurant (like the admin UI), or the superadmin role. Deletes a menu item the way the admin UI does: the item is marked deleted and disappears from the menu (it can be restored with `updateMenuItem` and `deleted` false). Call it with `dryRun` true first and ask the user to confirm before deleting. The change is not pushed to POS devices or third-party channels (Wolt, Foodora) immediately.

Requires the administration or administration servings delete permission in the restaurant (like the admin UI), or the superadmin role. Permanently deletes a quantity type (it cannot be restored). A quantity type which is still used by the quantities of any menu item cannot be deleted; the error tells how many entries use it, and those quantities have to be given another `quantityTypeId` with `updateMenuItem` first. Call it with `dryRun` true first and ask the user to confirm before deleting. The change is not pushed to POS devices or third-party channels (Wolt, Foodora) immediately.

Requires the stockmanagement inventories modify permission in the restaurant (like the admin UI), or the superadmin role. Finalizes an existing draft inventory (a stock count saved with `draft` true, for example by `createInventory`): it is not a draft any more and the stock is recalculated from the date of the inventory for every counted item, in the background (`stockRecalculation` started). This changes the stock and cannot be undone with this tool, so: 1) find the inventory with `getInventories` (the `draft` flag) and read its entries with `inventoryId`; 2) call `finalizeInventory` with `dryRun` true, read the `date`, the `store` and the entries (`count`, `unitSize`) back to the user and ask for confirmation; 3) call it again with `dryRun` false, once. A template, an inventory which is already final and an inventory with recipe based products are rejected (finalize those in the admin UI, Stock management, Inventories). `restaurantId` is the global restaurant id from getAuthorizedRestaurants; `inventoryId` is the restaurant's own id returned by `getInventories`.

Read only. Lists the advertisements (administration > advertisements) of a restaurant with their preview pictures, and the status of the webshop images (`webshopImages`: published, missing, not active, no image or duplicate). Requires the advertisements view permission in the restaurant, or the superadmin role. Every advertisement has `id`, `name`, `isActive`, `priority`, the validity (`fromDate`, `toDate`, `fromTime`, `toTime` in minutes, `days`; empty means always), the menu item and category ids it applies to, `hasImage`, the picture details and the public `url`. The advertisements named exactly `banner` (the banner image at the top of the webshop page), `banner_phone` and `banner_tablet` (the banner for phones and tablets), `footer` (the footer image), `background` and `logo` feed the webshop: an advertisement with one of these names which is active and has an image is published at `.../eatwithme.server/tableService/{restaurantId}/getImageByName/{name}` (the `url` of the result), so the CSS can use it, e.g. `body[theme="basic"] #generic-information { background-image: url(https://instance.eatwithme.online/instance11/eatwithme.server/tableService/1/getImageByName/footer); background-size: cover; }`. A name can be used by one active advertisement only. Advertisements named `ads_...` are shown by the POS and waiter apps. `restaurantId` is the global restaurant id from getAuthorizedRestaurants.

Return the restaurants this client is authorized to query. Call it first: every restaurant has a `restaurantId` (its global id), the value to pass as `restaurantId` to all other tools, together with its `instance`.

Use this for raw order-level stock consumption records from the tenant consumptionstockentry table. It is intended for detailed audit, traceability, and reconciling what was consumed by which order or menu item, not for summary stock totals or supplier purchasing recommendations.

Read only. Lists the incoming stocks (goods received from a supplier: invoices and delivery notes, the `Incoming stocks` of the admin UI) of a restaurant, the newest first, or returns one with all its entries (`deliveryId`). Requires the stockmanagement incoming stocks view permission in the restaurant, or the superadmin role; users restricted to stores see only their stores. Every delivery has `id`, `date`, `draft` (a draft does not change the stock), `supplier`, `invoiceId`, `deliveryNoteId`, `netTotal`, `bruttoTotal`, `createdBy`, `entryCount` and, with entries, `entries` (`entryId`, `menuItemId`, `name`, `unitSize` = what one received unit is, e.g. 1 kg, `count` = the number of units, `total`, `store`, `vatCategory`, `netUnitPrice`, `bruttoUnitPrice`, `netPrice`, `bruttoPrice`, `expiryDate`, `code`; `unmatched` true for an invoice line not yet matched to a menu item). The list result also has `suppliers`, `vatCategories` and `stores` to choose from when creating a delivery, and `total`, `offset`, `limit` for paging. This is different from `getIncomingStocks`, which is the report of the received entries. `restaurantId` is the global restaurant id from getAuthorizedRestaurants; all other ids are the restaurant's own ids, as used by the menu tools.

Use this to inspect delivered inventory entries for an authorized restaurant over a date range. It is meant for procurement review, supplier tracking, and stock-in history; not for order consumption or sales analysis.

Read only. Lists the stock inventories (stock counts) of a restaurant, the newest first, or its inventory templates (`template` true), or returns one with all its entries (`inventoryId`). Requires the stockmanagement inventories view permission in the restaurant (templates: inventories or inventory templates view), or the superadmin role; users restricted to stores see only their stores. Every inventory has `id`, `date`, `draft` (a draft does not change the stock yet), `store`, `createdBy`, `created`, `modifiedBy`, `entryCount` and, with entries, `entries` (`menuItemId`, `name`, `category`, `unitSize` = what one counted unit is, e.g. 1 kg or 0.7 l, `count` = the number of units counted, `total` = unitSize times count, `expiryDate`; `originalCount` with the stock view permission). A template has `templateName` and the entries to ask for when counting; template items which cannot be counted any more are in `skippedEntries` with the reason. The list result also has `stores` (id, name) and `total`, `offset`, `limit` for paging. `restaurantId` is the global restaurant id from getAuthorizedRestaurants; all other ids are the restaurant's own ids, as used by the menu tools.

Read only. Lists the inventory scrappings (disposals: wasted, spoiled, broken or otherwise written off stock) of a restaurant, the newest first, or returns one with all its entries (`scrappingId`). Requires the stockmanagement inventory scrapping view permission in the restaurant, or the superadmin role; users restricted to stores see only their stores. Every scrapping has `id`, `date`, `store`, `createdBy`, `created`, `modifiedBy`, `entryCount` and, with entries, `entries` (`menuItemId`, `name`, `category`, `unitSize` = what one scrapped unit is, e.g. 1 kg or 0.7 l, `count` = the number of units scrapped, `total` = unitSize times count, `expiryDate`, `comment` = the reason). The list result also has `stores` (id, name) and `total`, `offset`, `limit` for paging. `restaurantId` is the global restaurant id from getAuthorizedRestaurants; all other ids are the restaurant's own ids, as used by the menu tools.

Read only. Use this to see who changed the menu of a restaurant, when and what: the change log of menu items, menu categories and quantity types (created, modified, deleted, restored, activated, deactivated, moved, reordered), the latest change first. Requires the administration, menu change log or products full access permission in the restaurant (like the menu change log page of the admin UI), or the superadmin role. Every entry has `time`, `modifiedBy` (e-mail), `modifierName`, `source` (admin = the admin UI, mcp = this API), `entityType` (Meal, Drink, MealCategory, DrinkCategory, QuantityType), `entityId`, `entityName`, `modificationType` and `changes` (a list of {field, from, to}; `fromLabel` and `toLabel` hold the names of referenced categories, VAT categories, production lines and quantity types). Without `from` the last 30 days are returned (all the history of an entity when `itemId` or `categoryId` is given); entries older than one year are deleted. The result has `total`, `offset` and `limit` for paging. `restaurantId` is the global restaurant id from getAuthorizedRestaurants; `itemId` and `categoryId` are the menu ids returned by `searchMenuItems` and `getMenuStructure`.

Shows the pictures of a menu item or a menu category: the preview pictures and, per channel, the size, the last update, the public `url` and which picture the channel really uses. A menu item has a `default` (basic) picture, a `big` picture and an own picture for the channels `wolt`, `foodora`, `falatozz` and `choice` (ChoiceQR); a channel without its own picture uses the `big` picture, then the `default` one (`effectiveFrom` tells which). A menu category has only the default picture. Use it for questions like 'Show the picture of the Margarita Pizza' and 'Which picture does Wolt show for the Mojito?', and to check the result after `setMenuImage`. `restaurantId` is the global restaurant id from getAuthorizedRestaurants; `itemId` and `categoryId` are the ids returned by `searchMenuItems` and `getMenuStructure`.

Use this to inspect how a restaurant menu is structured: category hierarchy, item placement, mandatory/included ingredients (the recipe), optional add-ons, option groups, channel visibility (wolt, foodora, choice, kiosk, webshop, falatozz), available quantities (portion sizes with price, cost, default flag and per-channel availability), and price/cost/profit context for a specific menu item or category. The recipe is built from mandatory and included option ingredients, so this tool is best for questions like 'Explain how Margarita Pizza is set up' or 'What are the ingredients and options in Pizza category'. Option groups (optionGroups) reference an option category: if no items of that category are explicitly listed for the menu item (in optionalAdditions), every item of the option category is available; if items of that category ARE explicitly listed, the available items are restricted to only those explicitly listed items.

Read only. Returns the complete CSS of the restaurant (the `css` property of the restaurant, applied to the webshop and the apps) with its `length`, and the status (`webshopImages`) of the advertisements which feed the webshop images. Only a user with the superadmin role can use it for now. Use it first when the user wants to discuss or change the look of the webshop: show or summarize the current CSS, then change it with `setRestaurantCss`. The CSS typically imports a font, defines `:root` variables (colors, fonts) and styles `body[theme="basic"]` elements, with media queries for small screens. The advertisements named exactly `banner` (the banner image at the top of the webshop page), `banner_phone` and `banner_tablet` (the banner for phones and tablets), `footer` (the footer image), `background` and `logo` feed the webshop: an advertisement with one of these names which is active and has an image is published at `.../eatwithme.server/tableService/{restaurantId}/getImageByName/{name}` (the `url` of the result), so the CSS can use it, e.g. `body[theme="basic"] #generic-information { background-image: url(https://instance.eatwithme.online/instance11/eatwithme.server/tableService/1/getImageByName/footer); background-size: cover; }`. A name can be used by one active advertisement only. `restaurantId` is the global restaurant id from getAuthorizedRestaurants.

Use this to learn how a restaurant is configured and which options exist before creating or changing menu items and categories. Returns the restaurant profile (name, address, languages, default language, base currency, currencies, payment methods) and the option lists with their ids: `vatCategories` (for vatCategoryId), `quantityTypes` (for quantityTypeId), `timings` (the courses and whether each is enabled), `productionLines` (for productionLineIds) and `labels`, plus the restaurant `settings` tree (business day, service fee, enabled features such as takeaway, pickup, kiosk, webshop, Wolt, Foodora, menu and price calculation options, ...). The tree shows which settings exist and their current values. Use `path` (for example enabled-features/wolt) to read only one part of the tree, or `includeSettings` false to get only the option lists. Secrets such as keys, tokens and passwords are hidden. `restaurantId` is the global restaurant id from getAuthorizedRestaurants; all other ids in the result are the restaurant's own ids, as used by the menu tools.

Return the current active and connected status for a specific authorized restaurant. Does not expose service URLs or hostnames.

Use this for revenue, sales trend, and order-value analysis for an authorized restaurant over a date range. It returns transaction-level sales rows and staff attribution only; do not use it to identify guests, retrieve customer contact data, or infer personal identities.

Use this to find stock items that are below their desired level and to get supplier suggestions for reordering. Best for inventory replenishment planning and a quick purchasing shortlist, not for detailed historical transaction auditing.

Use this for aggregated stock movement reporting: opening stock, consumption, incoming goods, shortages, scrapping, outgoing movements, and final stock for a restaurant over time. It is designed for inventory analysis and trend reporting, not for raw order-level consumption details.

Lightweight flat list of the menu items of a restaurant (id, name, shortName, categoryId, categoryPath, unitPrice, active), searchable by name. Use this first to find the id of a menu item or to list the items of a category, then call getMenuStructure with itemIds only for the items whose recipe, options, channels or quantities you need. The name search is case and accent insensitive, every word of the search text must appear in the item name or short name. Deleted items are never returned.

Requires the same permission as modifying the menu item or category in the admin UI (administration, or products full access; stock list access is enough for items), or the superadmin role. Sets, replaces or removes a picture of a menu item or a menu category. `restaurantId`, `itemId` or `categoryId`, and the new picture (`imageBase64` = the raw Base64-encoded bytes of the picture, optionally as a data URI; a file path, file id or URL is not accepted) or `remove` true are required. `channel` selects the picture: `default` (the basic picture shown in the POS, waiter and online menu), `big`, `wolt`, `foodora`, `falatozz`, `choice` (ChoiceQR) or `all`; a category has only `default`. A channel without its own picture uses the `big` picture, then the `default` one, so set a channel picture only when it has to differ. Setting `default` also updates `big` when the item has no big picture or it is a copy of the default one, as the admin UI does. PNG, JPEG and GIF pictures are accepted (WebP, HEIC and SVG are not); a picture which is too large is scaled down (longest side 2000 px) and converted to JPEG automatically, transparency becomes white. `remove` deletes the picture of the channel. Call it with `dryRun` true first, show the returned `changes` to the user and ask for confirmation before saving; check the result with `getMenuImages`. The picture is only stored in the restaurant's own menu data, nothing is sent to Wolt, Foodora, Falatozz or ChoiceQR by this tool. The channel names only select which stored picture of the item is changed.

Only a user with the superadmin role can use it for now. PUBLISHES the CSS of the restaurant to its live, public webshop and apps: it replaces the `css` property of the restaurant, and customers see the new look after a page refresh. `restaurantId` and `css` (the COMPLETE new stylesheet, not a patch) are required: read the current CSS with `getRestaurantCss`, change it as discussed with the user and send the whole result. Call it with `dryRun` true first, tell the user what will change and that it goes live for the customers of the restaurant, and ask for confirmation before saving. The images of the page (banner, footer) are managed with the advertisement tools: The advertisements named exactly `banner` (the banner image at the top of the webshop page), `banner_phone` and `banner_tablet` (the banner for phones and tablets), `footer` (the footer image), `background` and `logo` feed the webshop: an advertisement with one of these names which is active and has an image is published at `.../eatwithme.server/tableService/{restaurantId}/getImageByName/{name}` (the `url` of the result), so the CSS can use it, e.g. `body[theme="basic"] #generic-information { background-image: url(https://instance.eatwithme.online/instance11/eatwithme.server/tableService/1/getImageByName/footer); background-size: cover; }`. A name can be used by one active advertisement only.

Requires the advertisements modify permission in the restaurant (like the admin UI), or the superadmin role. Changes the name, the active state, the priority or the picture of an advertisement (`imageBase64`, the Base64-encoded bytes of the new picture, replaces the picture, `removeImage` deletes it); the other fields (validity, menu items) are not changed. `restaurantId` and `advertisementId` are required. Use it to replace the `banner` or `footer` picture of the webshop, or to hide it with `isActive` false. Pictures are never fetched from public URLs, file ids or file paths: the picture is always uploaded in the call as `imageBase64`. The public `url` in the results is only where the stored picture is published, never an input. The advertisements named exactly `banner` (the banner image at the top of the webshop page), `banner_phone` and `banner_tablet` (the banner for phones and tablets), `footer` (the footer image), `background` and `logo` feed the webshop: an advertisement with one of these names which is active and has an image is published at `.../eatwithme.server/tableService/{restaurantId}/getImageByName/{name}` (the `url` of the result), so the CSS can use it, e.g. `body[theme="basic"] #generic-information { background-image: url(https://instance.eatwithme.online/instance11/eatwithme.server/tableService/1/getImageByName/footer); background-size: cover; }`. A name can be used by one active advertisement only. Call it with `dryRun` true first, show the returned `changes` to the user, tell the user that the change goes live in the webshop for the customers, and ask for confirmation before saving; check the result with `getAdvertisements`.

Requires the stockmanagement incoming stocks modify permission in the restaurant (like the admin UI), or the superadmin role. Changes an existing incoming stock: its supplier, date, invoice / delivery note numbers, draft flag (`draft` false finalizes it) and its entries. When the delivery is or was not a draft, the stock is recalculated in the background (`stockRecalculation` started). It changes the stock and cannot be undone with this tool, so: 1) read the delivery with `getIncomingStockDeliveries` (`deliveryId`); 2) ask the user what to change; 3) call `updateIncomingStockDelivery` with `dryRun` true, read the result (supplier, date, entries, totals) back to the user and ask for confirmation, especially when entries are removed; 4) call it again with `dryRun` false, once. To change entries send the complete list (see `entries`). A delivery with invoice lines not yet matched to a menu item (`unmatched`) can have its entries changed only in the admin UI. `restaurantId` is the global restaurant id from getAuthorizedRestaurants.

Requires the administration, products full access or stock list permission in the restaurant (like the admin UI; deleting, activating or moving needs administration or products full access), or the superadmin role. Modifies any parameter of an existing menu category: names, descriptions, flags, position, availability period, VAT, production lines, allergens, add-ons and option groups offered for its items (`menuItemAdditions`, `menuCategoryAdditions`), channel settings, moving it under another parent (`parentCategoryId`) and soft deletion. Only the fields that are present are changed. Ids are the menu ids returned by `getMenuStructure`. Call it with `dryRun` true first and show the returned `changes` (field, from, to) to the user before saving. The change is not pushed to POS devices or third-party channels (Wolt, Foodora) immediately. Inheritance: a category passes its settings down to its subcategories and items: course (`timing`), VAT, production lines, NTAK main and sub category, channel and other `settings`, and the add-ons and option groups (`menuItemAdditions`, `menuCategoryAdditions`). Every one of these can be overridden on an individual item, but a setting that is common to all items of a category must be set only on the category (the highest category where it is valid), not on the items. Set it on an item only when that item differs from its category, and do not repeat the category's value on every item. Create the option categories (the categories whose items are offered through option groups) under one top level 'container' category named Options (Opciók in Hungarian); reuse it if it already exists (check with `getMenuStructure`), otherwise create it first.

Requires the administration, products full access or stock list permission in the restaurant (like the admin UI; deleting or activating needs administration or products full access), or the superadmin role. Modifies any parameter of an existing menu item: names, descriptions, flags, prices and portion sizes (`availableQuantities`), cost, VAT, category, production lines, allergens, recipe ingredients and add-ons (`menuItemAdditions`), option groups (`menuCategoryAdditions`), channel settings and soft deletion. Only the fields that are present are changed, everything else is kept. All ids are the menu ids returned by `searchMenuItems` and `getMenuStructure`. Call it with `dryRun` true first and show the returned `changes` (field, from, to) to the user before saving. The change is not pushed to POS devices or third-party channels (Wolt, Foodora) immediately. Inheritance: a category passes its settings down to its subcategories and items: course (`timing`), VAT, production lines, NTAK main and sub category, channel and other `settings`, and the add-ons and option groups (`menuItemAdditions`, `menuCategoryAdditions`). Every one of these can be overridden on an individual item, but a setting that is common to all items of a category must be set only on the category (the highest category where it is valid), not on the items. Set it on an item only when that item differs from its category, and do not repeat the category's value on every item. Create the option categories (the categories whose items are offered through option groups) under one top level 'container' category named Options (Opciók in Hungarian); reuse it if it already exists (check with `getMenuStructure`), otherwise create it first.

Requires the administration or administration servings modify permission in the restaurant (like the admin UI), or the superadmin role. Renames a quantity type (the unit of the portions). `restaurantId`, `quantityTypeId` and `name` or `names` are required. All the menu items which use the quantity type show the new name (`usedByQuantities` in the result tells how many quantity entries use it). Call it with `dryRun` true first and show the returned `changes` to the user before saving. The change is not pushed to POS devices or third-party channels (Wolt, Foodora) immediately.