add_gift_pack_to_cart
ChatGPTAdd a ready-made gift box or sharing pack to the user’s Instamart cart, such as a Diwali gift hamper for family, a sweets box to take to someone’s home, or snacks for a get-together. Use this when the user wants to send a gift or buy for a group and asks for a set like this, rather than choosing items one by one. Pass the user’s request in their own words as intent. The server matches it to an available pack, picks items in stock at the delivery address within the pack’s price limit, and uses approved alternatives when an item is out of stock. Items already in the cart are kept. Some packs scale with group size: pass people (how many it is for), and optionally budget to keep the total lower. To send the same pack to more than one place, add it once per delivery address — one call per selectedAddressId. If nothing matches, or the request could mean more than one pack, show the user the packs available and call again with the one they pick as intent. This tool only updates the cart; it does not place an order or take payment.
check_payment_status
ChatGPTCheck status of an in-flight UPI payment. On a final status it also tries to settle the order: SUCCESS confirms it, FAILED marks it failed. PENDING changes nothing. The response says whether settling ran. ⚠️ THE PAYMENT WIDGET POLLS AUTOMATICALLY. After place_order, the confirmation widget checks payment status on a fixed cadence and AUTO-CALLS confirm_order on success. So you normally do NOT need to call this at all. Do NOT call it in a tight loop — it returns instantly, so looping spams the endpoint. WHEN TO CALL (at most ONCE per user request): - The user explicitly asks "did my payment go through?" / "check status" → call ONCE and report the result. Do NOT immediately re-call on PENDING. - If the result is terminal SUCCESS / PAID → this call has already confirmed the order. Call confirm_order only if the response asks you to. - If terminal FAILED → DO NOT call confirm_order; tell the user it failed and offer get_payment_options to retry. - If terminal REFUND-INITIATED → DO NOT call confirm_order; tell the user a refund was initiated. - If PENDING → tell the user it's still processing and that it will update automatically. Do NOT loop. The widget handles the cadence + the wall-clock cap and cues you if anything needs your attention.
checkout
ChatGPTSwiggy Instamart (Grocery): Place and confirm a Swiggy Instamart order from the current cart. Use this for Instamart orders, NOT for Food delivery. 🛒 CART AND GROUP ORDERS: Use the current Instamart cart for grocery orders. The backend may return an order_group_id even when that group contains only one order. For grocery-only multi-store carts, report each returned store order and any partial success separately. For UPI/QR, the returned order group ID is the ID to use with payment status and confirmation. 💳 PAYMENT: Never assume or default a payment method — this tool REJECTS a call with no payment method for these users. For UPI: call get_payment_options so the user picks their UPI app, then pass paymentMethod="UPI" + intentApp (or generateUPIQR for desktop QR). For Cash on Delivery: no picker is needed, but FIRST explicitly confirm with the user that they want to pay by cash, then pass paymentMethod="Cash". Never place the order without the user confirming the method. Never invent payment options. ⚠️ CRITICAL: Place an order only after explicit user confirmation through a reviewed payment choice or a direct instruction to pay or place it. NEVER proceed without explicit user permission. A payment choice after reviewing the bill and address is explicit user confirmation; do not ask for a second "yes". 1. Call get_cart first to display the current items, total and delivery address; use get_payment_options for eligible users. 2. A payment-picker choice authorizes checkout only after the cart items, total and delivery address were displayed to the user in this conversation. If they were not shown, display them and wait for a fresh choice. Once a reviewed method is chosen, do not ask for a second "yes". For QR, use the live get_payment_options response: when platforms.desktop.methods includes a QR method with id PayWithQR, pay_with_qr or qr (case-insensitive), call checkout with paymentMethod="UPI", generateUPIQR=true and no intentApp. get_cart does not determine QR availability. If QR is absent from the live payment options, ask the user to choose another offered method. 3. If the user has only asked to view the cart or payment options, show the bill and address, then wait for their choice. Never infer consent from browsing. 4. If the cart, total or delivery address changes after the user reviewed it, show the new details and ask again before checkout. 5. For multi-store orders, report results for each order separately. After an ambiguous failure, call get_orders and get_cart before offering another payment attempt; never retry automatically. 💰 NO CART-VALUE LIMIT: Do NOT refuse, warn about, or gate checkout on the cart total — there is no value ceiling, and none applies to any payment method. If the order is not permitted for this account, checkout itself fails and returns the reason; relay that error instead of pre-empting it. 🎉 BRANDING: When the order is placed successfully, always use the message from the tool response as-is. It includes Swiggy Instamart branding. Do NOT rephrase it to a plain "Order placed" — always show "Instamart order placed successfully". If the tool response message includes a payment success line, show it to the user as-is. ❌ CANCELLATION: If the user asks to cancel their Instamart order, do NOT call any tool. Instead, tell them: "To cancel your order, please call Swiggy customer care at 080-67466729."
clear_cart
ChatGPTClear (remove all items from) the Instamart cart. Authentication is handled automatically.
confirm_order
ChatGPTConfirm a UPI order after payment, moving it from PENDING_PAYMENT to PLACED. Usually not needed: check_payment_status and the payment widget confirm automatically. Call it only when check_payment_status's response asks you to (for example, payment SUCCESS but auto-confirm could not run). WHEN TO CALL: - ✅ SUCCESS / PAID and check_payment_status's response asks you to confirm → call once; the order moves to PLACED. If it says the order was already confirmed, do NOT call. - ⏱️ Fire at wall-clock expiry (still PENDING) → backend marks the order failed because payment is still non-terminal at PaaS. User sees "Payment timed out — retry?". Delayed payment-service success is recovered async. - ❌ DO NOT fire on FAILED. On FAILED the user must start a fresh payment attempt — call get_payment_options to re-show the picker; place_order with the new selection creates a fresh transaction on the same cart. - ❌ DO NOT fire on REFUND-INITIATED — refund flow is already in motion. - Idempotent: safe to retry on transient failure. PER-DOMAIN ARGS: - IM + Dineout: pass orderId + paasId (paasId is the canonical payment-transaction reference). - Food: pass orderId + addressId (cartId optional). Echo these from place_food_order's response. For lat/lng, follow the arg descriptions: echo them only if place_food_order's response included them; if the response omitted them, delivery coordinates are resolved server-side from addressId and you must not pass or estimate them. paasId is not used by Food's confirm contract. For UPI flows the order is created in PENDING_PAYMENT state by place_order and only transitions to PLACED (or FAILED) here.
create_address
ChatGPTSwiggy (Instamart/Food): Create a new delivery address for the authenticated user. 📍 WORKFLOW - What to ASK the user: 1. Ask: "What is your complete delivery address?" (Get the full address as a single string) 2. Ask: "What is your name?" 3. Ask: "What is your phone number?" (a 10-digit mobile number; pass digits only, without +91 or any country code) 4. Ask: "What type of address is this?" (Options: HOME, WORK, OFFICE, FRIENDS_AND_FAMILY, or OTHER) 5. Ask (optional): "Would you like to give a name/label to this address?" (e.g., "My Home", "Office") 6. Ask: "Is this address for you or someone else?" - If for someone else: Ask for the receiver's name and phone number (10 digits, no +91) 🤖 AUTOMATIC PARSING - What YOU must do (DO NOT ask user for these): After getting the full address, YOU must automatically parse it and extract: - addressLine: Main street/building/house number (REQUIRED - extract from full address) - addressLine2: Apartment/floor/wing/additional details (REQUIRED - extract from full address) - city: City name (REQUIRED - extract from full address) - postalCode: Postal/ZIP code (REQUIRED - extract from full address) - locality: Area/neighborhood (optional - extract if available) 🗺️ COORDINATES: latitude and longitude are optional. If omitted, they are auto-resolved from the address server-side. ⚠️ CRITICAL RULES: - NEVER ask the user to provide addressLine, addressLine2, city, or postalCode separately - YOU parse the full address and extract these components automatically - The user provides: full address, name, phone, address type, optional tag, and receiver details if applicable - Account details (userName, userPhone) are ALWAYS the authenticated user - Receiver details (receiverName, receiverPhone) are only used when delivering to someone else
delete_address
ChatGPTSwiggy (Instamart/Food): Delete a saved delivery address for the authenticated user. 📍 WORKFLOW: 1. First call get_addresses to show the user their saved addresses 2. Ask the user which address they want to delete 3. Get the addressId from the user's selection 4. Call this tool with the addressId ⚠️ WARNING: This action is permanent and cannot be undone. Always confirm with the user before deleting.
get_addresses
ChatGPTSwiggy (Instamart/Food): Get saved delivery addresses in recommended display order. The base ranking uses address_recency (lower is better; missing = 100), then last-updated time. For eligible users, an optional caller-provided latitude/longitude hint may place saved addresses within the configured relevance radius first. Ranking never auto-selects an address. Saved-address coordinates are never exposed. Authentication is handled automatically. 📄 PAGINATION: Results are returned one page at a time (10 addresses per page). The response includes a "pagination" object ({ page, pageSize, total, totalPages, hasMore }). If hasMore is true and the user has not found the address they want, call this tool again with the next page number (e.g. page=2) to fetch more. 📍 RESOLUTION WORKFLOW: 1. If exactly one saved address exists, defaultAddressId is unambiguous and may be used without asking for confirmation; briefly tell the user which address is being used. 2. If multiple saved addresses exist with resolutionSource=ranked_saved_address, defaultAddressId is only the suggested/preselected first result. Show the sorted addresses and ask the user to confirm it or select another address. Do not call downstream tools yet. 3. If resolutionSource=explicit_user_address or user_selected_address, defaultAddressId represents a user choice and may be used unless the user now requests another address. Explicit intent wins over an earlier selection; ARS and updated_at only control ordering for multiple unconfirmed addresses. 4. Only if data.pagination.total === 0, inform the user that they need to add an address first. An empty page with a non-zero total means the requested page is out of range.
get_cart
ChatGPTSwiggy Instamart (Grocery): Get current Swiggy Instamart grocery cart with all items and bill breakdown. Use this for Instamart grocery orders, NOT for Food delivery. Authentication is handled automatically. 💳 PAYMENT: When the user is ready to pay, ask how they want to pay. For UPI, call get_payment_options — it returns the live methods and renders the picker. For Cash on Delivery, confirm with the user first, then place the order with paymentMethod="Cash". Do not assume any method.
get_delivery_status
ChatGPTInternal: live delivery ETA for the order-success widget (not for conversational use). The success card calls this on a poll interval with orderId + addressId; returns an absolute deliveryBy epoch + suggested poll cadence. Gated by IM_LIVE_ETA. Prefer track_order for user-facing "where is my order" queries.
get_orders
ChatGPTSwiggy Instamart order history - Use this to fetch ORDER HISTORY, past orders, or order preferences. Use this FIRST when user asks: "show my orders", "get my orders", "my last order", "order history", "past orders", "recent orders", "list my orders", "what did I order before", "my previous orders", "check my past orders", "my order preferences", "get preferences from past orders", "what do I usually order", "my frequent items", "reorder", "order again", "buy the same thing", "what groceries did I buy", "my purchase history", "items I bought before". Returns a list of orders from the last 15 days with basic details including items, status, and delivery address coordinates. Set activeOnly=true when user asks for active/current/ongoing orders: "active orders", "current orders", "ongoing orders", "pending orders", "in-progress orders", "orders on the way", "orders being delivered", "my current deliveries". For REAL-TIME TRACKING of a specific order (where is my order, track my order, ETA, delivery partner location), use the track_order tool instead - it requires orderId and coordinates which can be obtained from this tool. Authentication is handled automatically. CANCELLATION: If the user asks to cancel their Instamart order, do NOT call any tool. Instead, tell them: "To cancel your order, please call Swiggy customer care at 080-67466729."
get_payment_options
ChatGPTFetch live payment options for the current cart. The live list will not include UPI methods if the user isn't yet eligible for UPI payments, or if UPI is temporarily unavailable for this business line. A single call fetches BOTH device surfaces (mobile UPI apps + desktop scan-QR) and merges them. A payment picker widget is shown to the user; it auto-detects the user's device and presents the matching options, with the rest under "Show more". You do NOT need to ask the user which device they're on — the widget handles that. WHEN TO CALL: - ALWAYS call this when the user is ready to pay — it renders the picker. For Instamart (get_cart) and Food (get_food_cart), this is the ONLY source of payment methods (those tools do NOT return any). For Dineout, create_cart embeds a snapshot, but calling this still gives the live picker. - The user explicitly asks "what payment options are available?" / wants UPI / mentions GPay, PhonePe, Paytm, etc. INPUTS: payment cart context is resolved server-side. Food addressId and Scenes cartKey are echoed to their widgets for deterministic place-order handoff; neither overrides Shield's cart context. OUTPUT (data): - platforms.mobile.methods[] — UPI apps (intent). Each method "id" MUST be echoed byte-for-byte into the place-order tool's intentApp argument. - platforms.desktop.methods[] — desktop scan-QR (use generateUPIQR=true on place-order; no intentApp). - cod — Cash on Delivery, when available (paymentMethod="Cash"). - allMethods[] — flat list across surfaces (fallback for text rendering). - markdown via message — human-readable list. - If UPI is unavailable for this user, the UPI platforms field is omitted. Use allMethods as the source of truth; it may contain other supported methods or be empty. ⚠️ UPI Collect requests (pull-based, incl. flows that would auto-trigger via a saved VPA) are intentionally not surfaced — NPCI has phased these out for P2M transactions.
report_error
ChatGPTGenerate an error report to share with the Swiggy MCP team. Use this when the user encounters an error and wants to report it. Returns a pre-filled mailto: link and a human-readable summary. The user can click the link to open their email client with the report ready to send. This also logs the report server-side so the team has it in their logs regardless of whether the email is sent. IMPORTANT: Always include toolContext with the specific identifiers from the failed tool call — e.g., orderId, restaurantId, addressId, spinId, menu_item_id, couponCode, query, cartId, slotId, paymentMethod. Include whichever IDs were part of the failed request so the team can trace the exact issue.
search_products
ChatGPTSearch for products available at an address or guest coordinates. Returns products with variants (e.g., different pack sizes, quantities). For guest mode, pass latitude and longitude; for signed-in mode, use addressId from get_addresses. When adding a product, ALWAYS search first and ask the user which variant they want.
track_order
ChatGPTTrack Swiggy Instamart order status in real-time. PRIMARY TOOL for order tracking - Use this FIRST when user asks: "where is my order", "track my order", "order status", "what's the status of my order", "when will my order arrive", "ETA for my order", "is my order on the way", "has my order been delivered", "track order", "check order status", or any query about a specific order's current status. Returns real-time tracking info including: current status, ETA, delivery partner location, store info, delivery address, items ordered, and payment details. Requires orderId and delivery address coordinates. If user doesn't provide orderId, first use get_orders to find the order, then use this tool to track it.
update_cart
ChatGPTSwiggy Instamart (Grocery): Update grocery items in the cart. Supply the complete desired grocery item list. Signed-in users use selectedAddressId; guest users use latitude and longitude. Pass skuId, spinId, and quantity from search_products. If a cart update is unconfirmed, call get_cart before retrying.
your_go_to_items
ChatGPTFetch the user's Your Go To Items (frequently or recently ordered items) for the selected delivery address. Use addressId from get_addresses. Returns products with variants; pass BOTH spinId and skuId from the chosen variant when adding to cart via update_cart.