Migros

Purpose Add products to the cart, incrementing any existing quantities. Does not set absolute quantities or provide final prices. Rules - A different store for addressId rebinds the cart and removes items not sold there; warn the user when this happens. - Use only unit or secondaryUnit returned for that product by searchGroceryProducts. For a new line, default to primary unit unless the user explicitly requests secondaryUnit. - Existing lines keep their current unit; changing it requires removing and re-adding the product. Positive Examples - "Add 3 apples" - "Add 500 grams of kıyma" Negative Examples - "Set milk to 2" -> updateInGroceryCart - "Remove milk" -> removeFromGroceryCart - "Find milk" -> searchGroceryProducts Chaining - After cart changes, use previewGroceryCart for authoritative totals and discounts before placing an order.

addToGroceryCart

Purpose List saved delivery addresses when the user asks to see, choose, confirm, or change one, or a downstream tool needs an unknown addressId. Rules - Skip lookup when a valid address is known and the user has not requested an address action. - Do not auto-select; wait for the user's choice. If none are saved, say so. - Preserve the user's label and preformatted City / Town details verbatim. Coordinates are for map display, not distance calculation. Positive Examples - "Show my delivery addresses" - "Switch to my work address" Negative Examples - "Add milk to my cart" -> addToGroceryCart when address is already known Chaining - Resolve labels such as "Home" or "eve" to a returned id before an address-dependent call; ask if ambiguous.

getDeliveryAddresses

Purpose Fetch the list of currently available service providers. Use a name from this response as `serviceProvider` in other tools. Rules - Skip if a provider is already known in context (user selected it, user named it, or a previous tool call used it). - Re-call only when the user explicitly asks to list, refresh, or change providers. - Never auto-select; after returning the list, wait for the user's choice before calling other tools. Positive Examples - "Where can I shop for groceries?" - "What services are available?" - "Which providers do you support?" Negative Examples - "Add milk to cart" → addToGroceryCart - "Search for chocolate" → searchGroceryProducts - "Show my delivery addresses" → getDeliveryAddresses

getProviders

Purpose Display the cart for a given address and provider with final priced state — discounts, delivery fees, availability, and the order gate. Rules - Authoritative for pricing. Re-call after any cart, address, or provider change; previous previews are stale snapshots. - `previewExpiresIn` bounds freshness; re-call if the user lingers past it. - `isOrderable` must be true before placing an order. - `discountTotal` excludes delivery discounts; `deliveryFeeNet` is post-discount. - If `delta.store` is present, the cart was REBOUND to a different store — warn the user. - If `delta.items` has entries, items were silently changed/removed — surface each one to the user: · "REMOVED" → item is no longer in the cart; `newQuantity=0`. · "CHANGED" → item stays; both `previousQuantity` and `newQuantity` are set. - Cart item product details include `isFavourite`, which is true when that product is in the user's favourites for the provider. You may mention favourite cart items when it is useful for the response. Positive Examples - "Show my cart and total" - "What's my final total with discounts?" - "Preview my order for my home address" Negative Examples - "Add milk to my cart" → addToGroceryCart - "Remove milk" → removeFromGroceryCart - "Set milk to 2" → updateInGroceryCart - "Search mascarpone" → searchGroceryProducts Response Presentation - Respond in natural Turkish prose; never echo field names (`subTotal`, `grandTotal`, `deliveryFeeNet`, …) or raw JSON. - Bad: "Ürün indirimi toplamı: discountTotal" - Good: "Sepet toplamınız 450,00 TL. Ürün indirimiyle birlikte ödenecek tutar 390,00 TL."

previewGroceryCart

Purpose Delete line items from the cart. Removes the whole line per productId (no partial decrement). Rules - Not authoritative for pricing; totals and discounts finalize in previewGroceryCart. - If `addressId` maps to a different store than the current cart, the cart is REBOUND and items not sold at the new store are REMOVED. Warn the user when this happens. - To reduce quantity without deleting the line, use updateInGroceryCart. - To empty the cart, remove all productIds from the current cart preview together in one call; an empty cart needs no removal. Positive Examples - "Remove milk from my cart" - "Delete Barilla spaghetti" - "Clear these two items from Hemen" Negative Examples - "Set milk to 1" → updateInGroceryCart - "Add two milks" → addToGroceryCart - "Search mascarpone" → searchGroceryProducts Chaining - After any cart change, call previewGroceryCart before placing the order to see authoritative totals.

removeFromGroceryCart

Purpose Search grocery products for a single delivery address. Multiple keywords for the same address go in one call as multiple `queries`; use this for product/SKU-level price, discount, availability, and stock questions. Rules - Results are snapshots. Re-call when the user asks to search, compare, or check prices again, especially after address or provider changes. - Use this tool when the user names a concrete product, brand, or category and asks for discounted, campaign, cheapest, price, availability, or stock results. - If the user asks for most-discounted or campaign products without a concrete product/category, ask which product or category to search before using this tool. - This tool returns search candidates and product-level discount signals; it does not provide a global product ranking by discount percentage. - If uncertain about `rootCategory`, you MAY include one duplicate query with `rootCategory` left empty. Never more than 2 variants per keyword. - Preserve each returned `items` list exactly as given. Do not reorder, regroup, deduplicate, or re-rank items unless the user explicitly asks. - `position` is the authoritative 1-based order within each returned `items` list. If you summarize or render results, keep the same order. - Each returned item includes `isFavourite` the product is in the user's favourites for that provider. You may mention or gently prioritize favourites when it helps the user's choice, while still preserving returned order unless asked otherwise. Positive Examples - "Find lactose-free milk at my home address" - "Show cheapest coffee in Hemen" - "Is milk discounted?" - "Search for coffee products on campaign" - "Find milk, bread, and eggs at my home address" Negative Examples - "What campaigns are available?" (not a product search) - "Are there any Tıkla Gel Al campaigns?" (not a product search) - "What are the most discounted products?" (ask "Which product or category should I search?", then use this tool after the user answers) - "Add milk to my cart" → addToGroceryCart - "What are the ingredients of Sütaş milk?" (not supported on this surface) Chaining - When feeding returned `productId` values to cart operations, pass the SAME `addressId` used in the search query.

searchGroceryProducts

Purpose Set cart items to absolute quantities, rather than incrementing or decrementing them. Rules - A different store for addressId rebinds the cart and removes items not sold there; warn the user when this happens. - Use the existing cart unit. To change units, remove the line and add it again with the new unit. - For zero quantity, use removeFromGroceryCart instead. Positive Examples - "Set milk to 2" - "Make ground beef 500 grams" Negative Examples - "Add 2 milks" -> addToGroceryCart - "Remove milk" -> removeFromGroceryCart - "Find milk" -> searchGroceryProducts Chaining - This result is not authoritative for pricing. After cart changes, use previewGroceryCart for final totals and discounts before placing an order.

updateInGroceryCart