Košík.cz

Show the customer's MANUALLY CURATED favorites list — items they explicitly marked as favorite on Košík ('Moje oblíbené'). This does NOT analyze purchase history; the list can be empty even for long-time customers who never starred anything. Call this tool ONLY when the customer: - asks about 'moje oblíbené' / their favorites list specifically - wants to see/manage the items they have starred For replenishment / 'co obvykle kupuju' / 'objednej jako minule' / 'doplň můj obvyklý nákup' — use get_frequent_products instead. That tool is auto-derived from real purchase history and is the right answer for questions about buying patterns. Returns a browsable product list with add-to-cart functionality. Each product includes cartQuantity showing how many are already in cart. If the list is empty, the customer hasn't starred anything — offer get_frequent_products (history-based) or search instead.

get_favorites

When to use: When the user asks about a specific past order, wants to see its items, or wants to reorder items from a previous purchase. Common workflows: (a) 'what was in my last order' / 'doplň co mi chybí z minulého nákupu' → first call get_order_history(limit=1) WITHOUT stateCategory (so an in-delivery ACTIVE order surfaces too — DELIVERED-only would miss it for a customer awaiting their first delivery), then this tool with the returned id; (b) for 'what do I usually buy' across many orders, use get_frequent_products instead — it does the aggregation server-side. Usage: Requires orderId (integer) obtained from get_order_history. Returns: Widget showing the order's items (with current product info needed for reorder), prices, delivery address, delivery window and payment method. The widget itself offers a 'reorder' action which adds items back to the cart via add_to_cart. Example prompts: 'Ukaž detail objednávky 12345', 'Objednej znovu to samé co minule', 'Z čeho mi došlo z minulého nákupu' (use AFTER get_order_history when only a number/date is known).

get_order_detail

When to use: When the user asks about previous purchases, order history, what they bought before, spending history, or wants to reorder a past purchase. Workflow shortcuts: (a) 'last order' / 'co jsem posledně koupil' / 'co mám v doručení' → call with limit=1 and NO stateCategory filter (so a recent ACTIVE / in-delivery order surfaces too — DELIVERED-only would miss it), then get_order_detail with the returned id to see items; (b) 'what do I usually buy' / 'replenishment' / 'co kupuji pravidelně' → DO NOT loop through orders here, call get_frequent_products instead — it aggregates across N past orders in a single server-side round-trip. Usage: Optional parameters limit (1-30, default 10), offset (pagination), stateCategory ('DELIVERED' = past completed orders, 'ACTIVE' = placed, awaiting delivery, 'ERROR' = failed/cancelled — usually NOT what the user means by 'order'), showArchived. Default (no stateCategory) returns ALL non-archived orders ordered most-recent-first, which is the right behavior for the common 'last order' question. Returns: Widget showing a list of past orders with id, number, date, state, total price and product count. To see items inside a specific order or to reorder, follow up with get_order_detail using the id from this response. Example prompts: 'Ukaž minulé objednávky', 'Co jsem posledně koupil', 'Historie nákupů', 'Co mám v doručení'.

get_order_history

When to use: When the user is ready to review the order before completing checkout (after delivery slot and payment method are set). Usage: Call AFTER set_transport_window and set_payment_method (or after user has chosen delivery time and payment). Returns: Widget showing delivery address, delivery window, payment method, and total price. Important: Always call order_summary before complete_order. Use this to show the summary and ask the user to confirm (e.g. 'Potvrdíte objednávku?'). Do not call complete_order until the user explicitly confirms. Example prompts: 'Ukaž shrnutí', 'Chci zkontrolovat objednávku', 'Potvrzuji objednávku' (show summary first, then finish on explicit confirm).

order_summary

When to use: When the customer asks what payment options exist or wants to browse/see payment methods. REQUIRED: Delivery address must be set first—call get_cashdesk_state to check; if deliveryAddress is not set, call get_delivery_address then set_checkout_delivery_address or create_delivery_address before this tool. Returns: Widget showing available payment methods (card online, cash or voucher at delivery, card at delivery / to driver). Wallet-based remember-card flows (Apple Pay, Google Pay, Skip Pay) are intentionally excluded. Do NOT use when the user has already stated they want a specific method (e.g. 'pay with card online', 'platba kartou')—in that case call this tool to get the list and ids, then call `set_payment_method` with the matching id. Example prompts: 'Jaké jsou platební metody?', 'Jak můžu zaplatit?', 'Ukaž mi způsoby platby'

get_payment_methods

Search for grocery products by fulltext or category. Use whenever the customer asks about products, wants to browse, or asks for food/recipe ideas. Fix obvious typos (e.g. 'chlebi' → 'chléb'). All filters (price_type, diet, allergens) work in both fulltext and category mode and combine freely. Query expansion — this tool does NOT expand queries automatically, you must do it: - Vague/occasion queries → call once per concrete term: 'party food' → search('chipsy'), search('pivo'), search('víno'), search('oříšky') - Recipe queries → search individual ingredients: 'guláš' → search('hovězí maso'), search('cibule'), search('paprika'), search('česnek') - When unsure, prefer multiple focused searches over one broad query. Bulk/occasion flow: when asked to buy for an occasion, call this tool with concrete terms, then immediately use the returned product IDs to call add_to_cart and then get_cart — do not stop to ask the user to confirm or type 'continue'.

search

When to use: When customer provides a delivery address (full address string) or wants to set address for checkout. Usage: Requires address ID from `get_delivery_address` response. Note: Customer can provide address as text (e.g., 'Václavské náměstí 796/42, 11000 Praha 1 - Nové Město'). Example prompts: 'Nastav adresu na Václavské náměstí 796/42, Praha 1', 'Doruč na mou adresu'

set_checkout_delivery_address

When to use: When customer wants to set or change tip amount. Usage: Requires tip amount in CZK (e.g., 50 for 50 Kč). Example prompts: 'Nastav spropitné 50 korun', 'Přidej 30 Kč spropitné'

set_checkout_tip

When to use: When customer wants to use or disable credit for checkout. Usage: Requires useCredit (true to use credit, false to disable). Returns: useCredit, creditAmount, usableCreditAmount, creditExpirationSoonAmount. Example prompts: 'Chci použít kredit', 'Použij můj kredit', 'Nechci používat kredit'

add_credit

Set the delivery note for the order. Updates the delivery address with the specified note text.

set_delivery_note

When to use: When the customer selects or states a specific payment method (e.g. 'pay with card online', 'chci platit kartou', 'hotovost'). Delivery address must be set first—call get_cashdesk_state to check; if not set, complete the address step (get_delivery_address then set_checkout_delivery_address or create_delivery_address) before this. You MUST call `get_payment_methods` first to get the list and ids, then call this tool with the matching payment method id. Do NOT only show the payment method widget when the user has already chosen a method—set it with this tool. Usage: Requires payment method `id` from `get_payment_methods` response. Returns: Updated cart prices. Example prompts: 'Zaplatím kartou online', 'Nastav platbu kartou', 'Chci platit hotově', 'I want to pay with card online'

set_payment_method

REQUIRED: You MUST call this tool in the SAME turn whenever the user selects or states a delivery time slot. Do not reply with text only (e.g. 'Doručení nastaveno', 'Nastavuji...', 'nastavím to')—calling this tool is the ONLY way to actually set delivery in the checkout. If you say delivery is set without calling this tool, it is a bug. Delivery address must be set first—call get_cashdesk_state to check; if not set, complete the address step (get_delivery_address then set_checkout_delivery_address or create_delivery_address) before this. Call `get_transport_windows` first to get available slots, then call this tool with the chosen slot's id, price, start, end, and proposition from that response. Example user messages that require calling this tool immediately in the same response: 'dnes 15-16h', 'chci dneska v 15-16h', 'chci dnes 15-16', 'zítra 16:00–17:00', 'Nastav nejbližší dostupný čas', 'Vyber ten první slot', 'Doruč v 15:00', 'Zítra v 10 ráno', 'Chci ten slot', 'Ano, ten čas mi vyhovuje', 'tak mi ho nastav'.

set_transport_window

When to use: When you need detailed transport/delivery information.

get_transport_delivery_data

When to use: (1) When customer asks about delivery times or time slots. (2) When customer says 'pokračuj k objednávce', 'prejdi k objednavce', or similar and get_cashdesk_state already returned deliveryAddress set + payment set + auxiliaryText like 'Vyberte prosím čas doručení'—then you MUST call this tool in the same turn to show the widget; never reply with text asking the user to type 'ukaž časy' or 'vyber termín'. The user must see the widget to choose a slot. Do NOT reply with only text listing times. REQUIRED: Delivery address must be set first (get_cashdesk_state; if not set, get_delivery_address then set_checkout_delivery_address or create_delivery_address). Returns: Widget with timeslots by day. If the response contains productsLimitations (non-empty list), some products in the cart restrict which timeslots are available. You MUST proactively inform the user about these limitations and help them pick a suitable transport window that works with all their products. Explain which products cause restrictions and suggest available timeslots that accommodate them. Examples: 'ukaz mi terminy', 'prejdi k objednavce' (when only slot missing), 'pokračuj k objednávce'.

get_transport_windows

Update an existing saved delivery address (contact name/surname/phone or other details). Pass the address text as given—the tool calls the suggest API and uses the first suggestion automatically. REQUIRED: address id (from get_delivery_address), address string, name, surname, phone (prefix + number), addressName, gps, street, city, zip. Always pass name, surname, phone; e.g. 'josef novak' → name='Josef', surname='Novak'. Optional: note, floorLevel, doorBell. Requires user login.

update_delivery_address

When to use: When customer wants to search for Dr. Max pharmacy products or add Dr. Max products to cart. This privacy setting must be enabled (set to `true`) to access Dr. Max products. Usage: Requires `value` (boolean: `true` to enable, `false` to disable). Set `value: true` to enable access to Dr. Max products. Important: This setting is required for searching Dr. Max products and adding Dr. Max products to cart. The setting only needs to be set once - once enabled (`true`), the value persists and does not need to be set again. If customer is searching for Dr. Max products or trying to add Dr. Max products and encounters issues, check if this setting needs to be enabled first. Returns: The current value of the pharmacy_drmax_gdpr setting (`{"value": true}` or `{"value": false}`). Example prompts: Customer searching for pharmacy/medication products from Dr. Max, or explicitly asking to enable Dr. Max product access.

update_privacy_settings