mark_action
Record that the human is about to click this action in the vendor app.
Instructions
Record that the human is about to click this action in the vendor app.
Side effects: appends {label, start, end} to .actions.json (creates the file).
Call while capture_start is running, immediately before each click; end times are closed
when the next mark arrives. Use the same label stem with different values (brightness 0%,
50%, 100%) so inference can fit scales. For an already-finished Wireshark capture without
markers, skip this and pass labels to report/diff_actions instead.
A label starting with 'seen' ('seen rpm 1180', 'seen rpm 1180 temp 34') is an observation,
not an action: what the vendor app displays right now. It does not end the current action
and is never diffed; analysis uses it to name and scale the device's reply readings
(rpm = raw, temp = (raw - 40) / 2). Mark it when the human reads a value off the screen.
On/off states ('seen pump on', 'seen pump off, alarm on') name single status-flag bits; words
('seen mode silent', 'seen mode turbo, rpm 3900': the word last or before a comma) name a mode
byte with a value -> word map; negative values ('seen temp -5') allow signed i8/i16 readings.
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": {
"label": "<label>"
},
"name": "mark_action"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| label | Yes | Action label, ideally with a value, e.g. 'brightness 50%' or 'color 255 0 0'; or an observation starting with 'seen', e.g. 'seen rpm 1180 temp 34' | |
| capture | No | Capture path whose sidecar markers file (<capture>.actions.json) is updated | capture.pcapng |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |