plan_multistep_inquiry
Break complex multilingual customer inquiries into a seven-stage execution plan, extracting order details and enforcing authentication and clarification gates before private lookups or account changes.
Instructions
Deterministically decompose a complex, multi-intent, or code-switched customer inquiry (supporting English, Spanish, Portuguese, French, German, Italian, Dutch, Polish, Banglish, Hinglish, and Spanglish) into a read-before-write 7-stage execution DAG (detect -> plan -> gate -> lookup -> clarify -> verify -> action). Runs completely offline with zero network calls or API key, extracting order IDs, emails, phones, and monetary figures while enforcing identity authentication and clarification gates before state mutations.
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": {
"message": "<message>"
},
"name": "plan_multistep_inquiry"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| message | Yes | Raw incoming customer message text (single-language or code-switched, single or multi-intent). | |
| localeHint | No | Fallback ISO language or script hint when no non-English tokens match automatically. | en |
| knownCustomerOrderIds | No | Previously retrieved order IDs on file for this customer so redundant order-number questions can be skipped. | |
| hasAuthenticatedSession | No | Whether the customer has already completed identity verification for private order/account lookups or mutations. |