confirmation-state
Classify a confirmation message as submitted, pending, reserved or completed from caller or default phrases — Reads a confirmation page, email or API message and decides which state it states: submitted, pending, reserved or completed, using phrase lists the caller supplies (preferred, because wording is provider-specific) plus an optional default English list. Matches are whole-word, case- and typography-insensitive, returned with offsets in UTF-16, code points, UTF-8 bytes and graphemes, and a match ins
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": {
"text": "<text>"
},
"name": "confirmation-state"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | Confirmation text. | |
| rules | No | Caller phrase lists; with these present the defaults are off unless useDefaults is true. | |
| precedence | No | When several states match, the first one listed wins. Without it a conflict is unknown. | |
| useDefaults | No | Include the default English phrases. Default true only when rules is absent. |