Send an order request (no payment)
request_quoteUse when: the user agreed to send their email address and the listed sets, and wants a confirmed delivered total (request="order") or an email when a set is available again (request="notify"). Do NOT use: if the user's request is vague (no set named, no country, or a budget without saying whether shipping and duties are included): call clarify_request first and ask its questions. Do NOT use it to pay, to reserve stock or to send names, street addresses, phone numbers or payment details. Returns: order_id and request_summary (or watch_id for notify). No payment and nothing reserved: a person on our team emails the confirmed delivered total; nothing is bought before the customer accepts. Send only these fields — never names, street addresses, phone numbers or payment details. Read request_summary back to the user. Retries: send idempotency_key (a UUID you keep for this one request); sending the same request again with the same key returns the same order_id instead of a second request (idempotency in the result says whether this call was retry-safe). Send provenance (where each value came from): a value that is not just_confirmed comes back in unconfirmed with a question (kind confirm) to ask the user. Example requests: "Order this Korean set for my sister in Seattle; email me the confirmed total first." / "이 세트 미국 시애틀로 주문 요청해 줘. 확정 금액은 메일로 먼저 받을게" / "このセットを大阪に送る注文を依頼して。確定金額を先にメールで"
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"ship_country": "<ship_country>",
"contact_email": "<contact_email>"
},
"name": "request_quote"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| items | No | ||
| options | No | choices for sets that have them, keyed by bundle_sku, e.g. {"<sku>": {"scent": "Cotton Haze"}} — values in list_sets sets[].options | |
| request | No | ||
| language | No | reply language tag, e.g. en, ja, es | |
| quantity | No | ||
| trace_id | No | optional: the trace_id an earlier clarify_request returned, so the steps of one request link up. Not personal data. | |
| bundle_sku | No | one set (use items for several sets) | |
| client_ref | No | your own task id, echoed in our log; not used for retries | |
| provenance | No | Optional provenance: where each value came from, keyed by bundle_sku or items, quantity and ship_country, each one of just_confirmed (the user said or confirmed it in this conversation), known_before, assumed or unknown. The request is still received; any value not just_confirmed comes back in unconfirmed with questions (kind confirm): ask the user before our email arrives. | |
| ship_region | No | state/province/prefecture name only — not an address | |
| ship_country | Yes | ||
| contact_email | Yes | one email address for the confirmed quote | |
| idempotency_key | No | optional retry key (e.g. a UUID) for this one request: the same key with the same request returns the same order_id. Without it, trace_id is used as the key when sent. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||