Stored scenarios
scenarioSave, validate, retrieve, and reverse-search stored macroeconomic stress cases; find the worst portfolio loss under a price or the lowest price reaching a loss level.
Instructions
Stored scenarios. Actions: list, get, save, validate, reverse.
Read guide(name="scenario-from-corpus") before building one. save checks the
contract and writes scenarios/<id>.json; validate loads the macro and satellite
versions the file names and names every problem that keeps the scenario from being
computed, including corpus fragments not visible on the calculation day when the index
exists, and reports how the elements are marked and what the scenario leaves unsaid
under labels and warnings. reverse searches the scenario's family on
portfolio: the worst loss under the price kappa, or the lowest price whose loss
reaches level. bench returns the text of the bench event and starts its
journal of corpus calls; build the scenario by the guide, then bench_save checks
spec and keeps it with the journal and notes in the bench results, beside an
empty review the expert fills. A bench scenario is never approved and never computed.
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": "scenario"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | The scenario id, which is also the name of its file: lowercase letters, digits and dashes. | |
| seed | No | The seed of the reverse search: the same inputs give the same answer. | |
| spec | No | The scenario specification save checks against the contract before it writes the file. | |
| draws | No | How many paths the reverse search draws on every point of the family. | |
| event | No | The bench event bench and bench_save work on, like E017. | |
| kappa | No | The price the reverse search fixes, for the worst loss under it. | |
| level | No | The loss level the reverse search finds the lowest price for. | |
| notes | No | What bench_save adds to the journal of the event: how the numbers of the scenario were chosen. | |
| action | Yes | What to do: list, get, save, validate or reverse. save overwrites a scenario stored under the same id. bench starts the scenario of a bench event, bench_save keeps it in the bench results. | |
| portfolio | No | The portfolio whose losses the reverse search measures. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||