The person's saved checks
scout_saved_checksList, save, run, or delete named guided checks to reuse UI test plan choices without storing passwords, codes, tokens, or cookies; run builds a new confirmable plan.
Instructions
List, save, run or delete the person's saved guided checks. A saved check keeps the choices of a guided plan under a name (the address, what to check, the journey, how they sign in, the care level and how thorough), never a password, code, token or cookie, in the project's .scenescout/guided/ folder, readable by its owner only. "save" takes a name and the planId of a plan built from choices (a re-check is not saved). "run" builds a new plan from a saved check, unaccepted: where its care level needs the person's confirmation, scout_guided_confirm asks them again. Follow that plan as scout_guided_plan's. "delete" removes one saved check's file and nothing else. With no check open in this conversation, pass the site's address so SceneScout finds its folder. Touches no browser.
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": {
"action": "<action>"
},
"name": "scout_saved_checks"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | The saved check's name: letters, digits, spaces and dashes | |
| action | Yes | "list", "save" (name and planId), "run" (name) or "delete" (name) | |
| planId | No | With "save": the plan whose choices to keep | |
| address | No | The site, when no check has run in this conversation: its saved checks are in the folder SceneScout keeps for it |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| plan | No | ||
| saved | Yes | ||
| folder | Yes | ||
| refused | Yes |