ticket_create
File a support ticket when something went wrong (a check, an order, payment, or printsi itself). With --order, the order's history is attached. A person reads every ticket; replies go to the email that paid for the order.
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": "ticket_create"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| No | Where to reply when there's no order (the user's own address, only with their permission). As an object: US {name, line1, city, state, postal_code}; Hong Kong {name, line1, district, area, phone, email, country: "HK"}. | ||
| order | No | The order it's about (ord_…), if any. | |
| message | Yes | What happened and what you expected (10–4000 characters). Include error codes and request ids. | |
| subject | No | One-line summary (defaults to the message's first line). | |
| category | No | One of: order_problem, check_problem, payment, bug, question, other. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes | ||
| data | No | ||
| error | No | ||
| summary | No | ||
| warnings | No | ||
| next_actions | Yes |