Luckin Coffee Order Assistant

Problem

Ordering Luckin Coffee is more than picking a drink: it requires confirming a shop, matching the right product spec, checking price and discounts, and handling payment plus pickup code. The my-coffee skill turns those scattered actions into a structured conversation, calling the Luckin order interfaces in a fixed sequence to reduce manual back-and-forth and parameter mistakes.

How It Works

• Location and shop: use queryShopList to find shops, then let the user confirm the shop before saving deptId; distance is shown only when the user provides exact latitude and longitude.
• Products and customization: match sellable products with searchProductForMcp; for cup size, temperature, sweetness, or milk base, use queryProductDetailInfo and switchProduct to select the correct SKU.
• Order and payment: run previewOrder first to get final price, discount amount, and couponCodeList, then createOrder; display only payOrderQrCodeUrl and keep the full payment link.
• After ordering: support queryOrderDetailInfo for status and pickup code, and cancelOrder for cancellation; do not reveal pickup info before payment is completed.

Boundaries

This skill is for in-store pickup and does not handle delivery. Real MCP calls need a complete token; placeholder or masked values can fail, and tool schemas should be read before first calls. Confirm shop, product, and payment impact with the user before creating an order.