Carrefour Belgique - België

Display the checkout button so the user can finish their order on the retailer website. Use this instead of telling the user to go to the retailer website manually when they are ready to checkout. The button opens the synced basket on the store website (same destination as the basket checkout button, without showing the total price). When to use: - After adding products or recipes to the basket and the user wants to complete their purchase - When the user asks how to checkout or where to pay - When you would otherwise instruct the user to open the retailer website to finish their order

render.checkout.button

Display product search results in the product carousel widget. IMPORTANT: To always use when a product.search is done. Workflow: 1. Call product.search as many times as needed to satisfy the user request (e.g. multiple searches for different criteria, or to get enough results). 2. IMPORTANT: Choose the best products to show based on the user request and the search results. The search can show irrelevant products, it is your job to pick the best ones to enhance User Experience. 3. Use the tool with the chosen products from step 2 to render the widget. IMPORTANT: pass the exact searchTerm you used in product.search as the top-level `searchTerm` field. IMPORTANT: when product.search returned a per-product `searchTerm`, include it — do NOT strip it. IMPORTANT: each product MUST include at least one of `image` or `imageUrl` copied from product.search — required for widget thumbnails; omitting both fails tool validation. If a catalog item has no image, omit that product from the payload. 4. Then provide a short textual summary. IMPORTANT: You MUST NOT render irrelevant products. Example: DO NOT RENDER 'compote de bananes' when a user asks for 'bananes'. The point of sale id is optional and will be used to render the widget for a specific point of sale.

render.product.carousel

Display detailed product information in the product detail widget. Workflow: 1. Call products.get_details to fetch enriched product data (nutrition, ingredients, labels, etc.). 2. Use this tool with the returned products to render the visual widget. Use this when the user explicitly wants to *see* product details in a visual format. If multiple products are provided, the widget includes navigation controls to browse products.

render.product.detail

Display product results in the product list widget. To ALWAYS use when a user asks to do its shopping list or equivalent. Workflow: 1. Call basket.get first when the user wants weekly shopping — inspect existing basket entries before proposing new products. 2. Call shopping_list.search as many times as needed to satisfy the user request (e.g. multiple searches for different criteria, or to get enough results). 3. If a product is missing or irrelevant, call product.search to search broader and find a replacement. 4. IMPORTANT: If one or many products are irrelevant even after re-searching, remove them from the list and ask for replacing them. 5. Use this tool with the final set of products you want to show (aggregate or pick from the search results) to render the widget. Each product MUST include the `searchTerm` field (required) — the ingredient or item name searched to find that product (e.g. "lait entier", "oeufs bio"). Each product MUST include at least one of `image` or `imageUrl` copied from search — required for widget thumbnails; omitting both fails tool validation. If a catalog item has no image, omit that product from the payload. 6. STOP after rendering — wait for explicit user validation (widget button or verbal approval). NEVER call basket.add_product until the user confirms. The point of sale id is optional and will be used to render the widget for a specific point of sale.

render.product.list

Display recipes in the recipe carousel widget. Workflow: 1. Call recipe.search as many times as needed to satisfy the user request (e.g. multiple searches for different criteria, or to get enough results). 2. Use this tool with the final set of recipes you want to show (aggregate or pick from the search results) to render the widget. The point of sale id will be used to render the widget for a specific point of sale. Guests: omit guests unless the user explicitly requested a guest count. When omitted, add-to-basket uses each recipe's native numberOfGuests (fallback: 4).

render.recipe.carousel

Use this when the user wants to clear or empty their shopping basket. This will remove all items and reset the basket to an empty state. When to use: - User asks to "clear my basket" or "empty my cart" - User wants to start over with a new basket - User asks to "remove everything from my basket"

basket.reset

Search for points of sale (shops) based on location. This tool uses geolocation-based search within a 50km radius. Calling this tool automatically renders an interactive store locator map widget — do NOT list or describe stores in text. Usage: - Use this when the user wants to find stores near a location, or when another tool needs a pointOfSaleId and the user has not chosen a store yet. - Prefer city name or postal code only (e.g. "Paris" or "75001"). Do NOT pass a full street address (no street number, street name, or apartment) unless the user explicitly gave only that and no city/postal code is available. If the user names a neighborhood or area, use that or the enclosing city, not their home address. - Present returned stores by name and address only; wait for the user to choose one store. - Present stores to the user using ONLY name and address (optionally as a numbered list). NEVER include id, pointOfSaleId, point_of_sale_id, or any numeric store identifier in messages visible to the user. After the user picks a store by name, address, or list number, reuse the matching id from structuredContent only inside subsequent tool calls (basket.initialize, basket.set_store, product.search, etc.). Never invent or default a store id.

point_of_sale.search

Use this tool to find products in a specific store (point of sale). This tool uses token-based search and a custom algorithm to find the best products. When to use: - If the search intent is clear, translate it to French and use it to find very specific products. Example: - USER: "I need 6L of plain milk" - Call with searchTerm = "lait entier 6L" - If the search intent is not clear, use a broad French searchTerm and let the API find the best matches. Example: - USER: "I am searching for eggs" - Call with searchTerm = "oeuf" IMPORTANT: Search terms must always be in French, even when the user writes in English or Dutch (e.g. "lait" not "milk", "pâtes" not "pasta", "tomate" not "tomato"). IMPORTANT: Always use singular form for the searchTerm (e.g., "oeuf" instead of "oeufs"). Note: This tool is specialized for cooking products (raw ingredients). If the user wants to find products to cook a recipe, use French ingredient names as searchTerm (e.g., "oeuf", "tomate", "oignon"). Also any spicification of a product must not be included in the searchTerm but in the optimization field if possible. IMPORTANT: Tool results may be not relevant to the user request. You MUST post filter results and only render relevant products. DO NOT MENTION IRRELEVANT PRODUCTS in your response.

product.search

Search for products in a shop that corresponds to the user's shopping list. Use this tool to show the user a list of real products for multiple items (e.g., a shopping list). It always returns products available in the specified store. IMPORTANT: - Always use singular form for search terms (e.g. "egg" not "eggs"). - Search terms must use the active conversation locale, matching the languageId resolved from the LLM/client locale (for example French terms for fr, Dutch terms for nl). - Use simple search terms, avoid complex ones (prefer 'tomates' over 'tomates rondes') unless the user specifically asks for a specific type of tomato. DISPLAYING RESULTS: - If the list of products is long, format the results to be concise. - Do not detail each product unless explicitly requested. - NEVER call basket.add_product from search results — call render.product.list and wait for user validation first.

shopping_list.search

Use this tool to find recipes based on meal names, specific ingredients, dietary restrictions, or meal types. This tool searches a comprehensive recipe database and returns recipes matching the criteria. When to use: - User asks for recipe suggestions or ideas -> you fill the parameters according to the user request. - User wants recipes with specific ingredients -> use the user query to fill parameters. - User has dietary requirements (vegan, vegetarian, gluten-free, lactose-free). - User wants specific meal types (starter, main dish, dessert, drink). Important notes: - By default returns main dishes unless user specifies otherwise. - The search is keyword-based (token-based), not semantic. Use specific French keywords rather than full sentences. - Search terms must always be in French, even when the user writes in English or Dutch (e.g. "lait" not "milk", "pâtes" not "pasta", "tomate" not "tomato"). Translate titleTerm and ingredient filters from the user message before calling this tool.

recipe.search

Update the quantity or replace a product in the basket. To replace: set selectedProductId and entryName (ingredient label). Optionally set quantity to preserve line quantity. To change quantity: set quantity (must be >= 1). To remove a product entirely, use basket.remove_product instead.

basket.update_product

Use when the user wants to change the number of guests/servings for every recipe in the shopping basket. Applies the same guest count to all recipe lines via synced servings.

basket.update_guest_count