Validate internet order
validate_orderStart: {"lookup_id":"","offer_id":""}. Poll: {"checkout_id":""}. Edit: {"checkout_id":"","expected_revision":,"details":{}}. Use exactly one shape. Customer, installation, consents and internet_addons belong inside details, never at the root. Start a checkout only when the customer asks to order. Each call waits for progress; while checking, poll with checkout_id only. Edits restart validation. On stale expected_revision, retrieve with checkout_id only before editing at the current revision. required_fields defines the contract; field_errors identifies actual missing/invalid fields relative to details. Refreshes the offer and returns an exact review without submitting an order. When preferred installation dates are required, provide both first and second choices using a time_window value allowed by the input schema. Installation type must be self or professional. Record the customer's explicit true or false choices for auto-pay and paperless billing; never enable them silently. Match the customer's equipment preference using returned equipment_options and catalog facts. Customer-owned equipment, included provider equipment and optional paid equipment are different choices. A free provider gateway does not satisfy an own-equipment request. Price or included status alone does not establish ownership. If an offer lacks the requested option, inspect another qualified offer or explain the limitation and ask the customer to choose; never fabricate an option. Send the complete selection in details.internet_addons using returned option_id and quantity values. Omit it to preserve current/default selections; [] declines optional items. Select at most one radio option and retain dependent parents. Ready means technically valid, not necessarily correct for the customer. Compare the entire review with the customer's budget, speed, equipment, billing and installation choices. Resolve mismatches before requesting authorization. Present every returned charge, discount, condition and unknown; do not invent a price adjustment for declined auto-pay or paperless billing. Never repeat the service PIN or full date of birth, even if supplied earlier. Keep capability IDs, terms_hash and validation_token out of customer-facing prose. Obtain explicit authorization for this exact current review before create_order; shopping intent or validation alone is not authorization.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "validate_order"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| details | No | ||
| offer_id | No | ||
| lookup_id | No | ||
| checkout_id | No | ||
| expected_revision | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| error | No | ||
| review | No | ||
| status | Yes | ||
| revision | No | ||
| expires_at | No | ||
| terms_hash | No | ||
| checkout_id | No | ||
| next_action | No | ||
| field_errors | No | ||
| schema_version | Yes | ||
| required_fields | No | ||
| validation_token | No | ||
| equipment_options | No | ||
| retry_after_seconds | No |