List scenarios
list_scenariosThe app's scenarios — what its checks look at: each with scenario_id, title, description, its expectations (what the description says must be seen, in its own words — a check answers each one), who wrote it (the team or the check), whether it is checked every time (daily), whether it is critical — walked on every check, whatever changed — with price_per_deploy_usd (what walking it adds to a check), and its last result. retired: true lists the ones no longer checked instead, with when and why each was retired. confirmation: a scenario the check found is to_decide until the person says to watch it — no daily or deploy check walks it before that — or not_journey; to_decide: true lists only those, and confirm_url is the page where the person decides.
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": {
"app_id": "<app_id>"
},
"name": "list_scenarios"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| team | No | Act in another of your teams, by its name or id (whoami lists them). Omitted: the key's own team | |
| app_id | Yes | App id from list_apps or create_app | |
| retired | No | true: the scenarios no longer checked instead — when and why each was retired | |
| to_decide | No | true: only the scenarios the check found that wait for the person's decision |