MCP Overview

​

Connecting

https://eleme-gateway.hicaspian.com/mcp/v1

​

Authentication

Authorization: Bearer clw_<32-hex>

{
  "consent_grant_id": "cg_...",
  "shop_id": "...",
  "...": "..."
}

​

Tool contract

• Parameters: passed as a JSON object. Every business tool carries consent_grant_id (the binding tools are the exception); cross-step IDs (cart_id / quote_id / preview_id / confirmation_token, etc.) are issued by the gateway and must be passed back verbatim — never fabricated or reused across flows.
• Responses: structured JSON; see each tool page for its full fields.
• Errors: the unified {"error": {"code", "message"}} format. See Error handling.

​

Multilingual

• At binding time: pass lang to request_user_bind. Every later call for that user uses this language, so you don’t pass it again.
• Per call: pass lang on a supporting tool; it affects only that call.

​

Bilingual responses

• Off by default: without include_chinese, or with it set to false, the response never has <key>_zh. Only an explicit true returns the Chinese original.
• Pass it together with lang: set lang to the target language (e.g. en) and include_chinese to true at the same time.
• When lang is Chinese (zh) or not passed at all, include_chinese has no effect and never errors — a Chinese response is already Chinese, so there’s nothing to attach.
• Scope matches single-language lang: set it at binding time via request_user_bind, or per call on any tool that accepts lang. The binding-time include_chinese only applies when this call passes neither lang nor include_chinese. As soon as a call passes lang, include_chinese for that call falls back to its default (false) instead of inheriting the binding-time setting — pass both together whenever a single call needs bilingual output.

{
  "shop": {
    "shop_id": "shop_xxx",
    "name": "Zhang Liang Malatang (Xixi Beiyuan)",
    "name_zh": "张亮麻辣烫(西溪北苑店)",
    "available": true
  },
  "items": [{
    "item_id": "item_xxx",
    "name": "Deluxe Single Meat Roll Set",
    "name_zh": "豪华单人肉卷套餐",
    "category_name": "Value Sets",
    "category_name_zh": "特惠套餐",
    "price": 5588,
    "image_url": "https://cube.elemecdn.com/...",
    "sku_options": [{
      "sku_id": "sku_xxx",
      "name": "Beef Roll Set",
      "name_zh": "肥牛卷套餐",
      "price": 5588
    }],
    "tags": ["Milk Tea", "Dessert"],
    "tags_zh": ["奶茶", "甜品"]
  }]
}

• Same type as the original field, no exceptions. A string field pairs with a string; a string-array field pairs with a string array of the same order and length (see tags / tags_zh above).
• Only appears when that field was translated successfully this time. No _zh means this field wasn’t translated this time, and the field itself is Chinese — you can check translation success field by field, with no need to check any other status field in the response.
• Only covers merchant data — shop names, item names, specs, add-ons, labels, and the like. Prompts generated by the platform itself (opening-hours notices, minimum-order-gap notices, etc.) are single-language only and never get a _zh.
• item_id / sku_id / price / image_url, coordinates, and timestamps aren’t language-specific and never get a _zh.
• delivery_fee_text (the delivery-fee display text, e.g. “Delivery ¥2”) is an exception: it never gets a delivery_fee_text_zh, even when translation succeeds. The delivery fee amount itself is in the delivery_fee field (a number) and isn’t language-specific.

// Target language only: drop every _zh
function stripZh(node) {
  if (Array.isArray(node)) return node.map(stripZh);
  if (node && typeof node === "object") {
    const out = {};
    for (const k of Object.keys(node)) {
      if (k.endsWith("_zh")) continue;
      out[k] = stripZh(node[k]);
    }
    return out;
  }
  return node;
}

// Chinese only: use _zh where present; no _zh means the field is already Chinese
function preferZh(node) {
  if (Array.isArray(node)) return node.map(preferZh);
  if (node && typeof node === "object") {
    const out = {};
    for (const k of Object.keys(node)) {
      if (k.endsWith("_zh")) continue;
      const zhKey = k + "_zh";
      out[k] = preferZh(zhKey in node ? node[zhKey] : node[k]);
    }
    return out;
  }
  return node;
}

​

Tool list

​

Authorization

​

Shops

​

Addresses

​

Ordering

​

Payment

​

Ordering flow

1. search_shops → returns shop_id + cart_id (cart_id already encapsulates the delivery coordinates)
2. get_shop_menu → pick items, get item_id / sku_id
3. quote_cart → price the cart, get quote_id
4. select_address → get address_id
5. preview_order → get preview_id + confirmation_token
6. create_order → get order_id
7. get_sign_action → complete payment via password-free signing