% Arabica UAE

Use this to load available items from a store. INTENT ROUTING: 1) If the user is in step-by-step browsing (City -> Store) and has not asked for specific items yet, call arabica.get_menu_categories next. 2) If the user asks for specific item names or a search-style request (e.g., "latte", "find croissant", "show menu"), call this tool directly. 3) For step-by-step category browsing, pass categoryId/categoryTitle to filter to one category. 4) Use showFullMenu=true for direct item/search intents, explicit full-menu requests, or checkout/order-building ID resolution. 5) PHOTO REQUEST RULE: If the user asks for a photo/image/picture of an item (including when itemId is already provided), do NOT answer from this tool output. You MUST call arabica.get_item_details with that exact itemId and render its widget. RAW URL RULE: Never paste item image URLs directly in chat. PAYLOAD RULE: Do not include optional customization options unless the customer explicitly requested them.

arabica.get_store_menu

Use this when you need to list all coffee stores in a specific city, including status labels like (Closed) and (Busy). Do not use if you already have the store details the user is looking for. Always present these options as a numbered list (1, 2, 3...) to make it easy for users to choose by number. This tool fetches live store status by default; set forceRefresh=false only if you explicitly want cached results. The result also includes store timing data (`todayStoreTiming` and `storeTiming`) for timing-related questions.

arabica.get_stores_in_city

Use this to retrieve the authenticated user’s account details (name, email, phone, loyalty points, credit balance). If the profile phone number is blank, show the phone number entry widget and call this same tool again with phoneNumber to update the existing profile. Do not use a separate profile-update tool.

arabica.get_user_account

Use this to retrieve the authenticated user’s recent orders. Optional storeId: when omitted, the tool uses the current store from private session context; if unavailable, it falls back to 0 (all stores). Always present results as a numbered list (1, 2, 3...).

arabica.get_user_order_history

Vehicle plate lookup — for car pickup ONLY. Do NOT call this tool unless the user has explicitly chosen "car pickup" as their pickup method. Never call for walk-in orders. When called with no query/selectVehicleId, returns saved plates with the most recently added one pre-selected by default. Show the widget and ask the user to confirm the pre-selected plate or choose another. Only ask for a new plate number if the returned list is empty. Supports selection via vehicle ID or natural query (number/index/plate text, e.g., "2", "ABCD", "same as yesterday").

arabica.get_user_vehicles

Use this ONLY when the user explicitly asks to browse/list cities. Do not call this just because store details are missing. If store/city is missing, ask the user to specify the store first. Never assume a city (for example, do not default to Dubai).

arabica.list_cities

Marks customer as arrived at store pickup point. Widget-only action from order status.

arabica.iam_here

MANDATORY ACTION after order creation OR to track status. Displays the final order status receipt. Do NOT call checkout_order if you already have an order ID.

arabica.get_order_status

Save selected customization options for an item so the server can reuse them during checkout if the client fails to pass selections.

arabica.save_item_selections

Use this when you need to find a city by its name using fuzzy search. Do not use for browsing; use arabica.list_cities instead. Only use this when the user explicitly mentioned a city text. If no city is provided, do not guess one; ask the user to provide city/store details. Always present store results as a numbered list (1, 2, 3...) so users can choose by number. This tool fetches live store status by default; set forceRefresh=false only if you explicitly want cached results. The result includes timing data (todayStoreTiming and storeTiming) for timing-related questions.

arabica.search_city

Use this when the user mentions a specific item name (e.g., "Latte", "Croissant"). This searches across ALL categories in the selected store menu. For multi-item orders: run this for each requested item name until all items are resolved. Do not stop after finding the first category. After all requested items are resolved to valid item IDs, do not call search_menu again before checkout unless the order changes. AUTO-PROCEED RULE: If exactly ONE item is found (no conflict) and the user's intent is to add/order it (e.g., "add", "please add", "I want", "include"), call checkout_order IMMEDIATELY with the resolved itemId. Do NOT ask the user to confirm, tap, or select anything — the item has already been identified unambiguously. TEMPERATURE RULE: When results include both a hot AND an iced/cold version of the same drink (e.g. "Hot Spanish Latte" AND "Iced Spanish Latte"), you MUST ask the user "Hot or iced?" before doing anything else. NEVER infer temperature from size defaults, item order, price, or any other factor. This is non-negotiable — do not skip it even if one version seems to match other details the user mentioned. PHOTO REQUEST RULE: If the user asks for a photo/image/picture of a matched item, immediately call arabica.get_item_details for that itemId and show its widget. RAW URL RULE: Never paste item image URLs directly in chat. If an exact match is not found, automatically suggest the closest similar items from the same store menu. Do not ask the user to browse categories first. Do not add optional options unless explicitly requested by the customer.

arabica.search_menu

Use this when you need to find specific coffee stores by name or part of their name across all cities. Do not use if the user is already browsing a specific city. Only use this when the user provided a store/city term to search. If location is missing, do not invent a query and do not assume a city; ask the user to specify a store/city. Do not auto-call arabica.list_cities. Always present store results as a numbered list (1, 2, 3...) so users can choose by number. This tool fetches live store status by default; set forceRefresh=false only if you explicitly want cached results. For timing/opening-hours questions, use the returned todayStoreTiming and storeTiming fields to answer directly.

arabica.search_stores

Shows the Noon Payments checkout widget after an online payment order is created. Called automatically by the checkout widget when paymentMethod is "online".

arabica.show_noon_payment