Stored portfolios
portfolioManage stored position sets: list, retrieve, save, delete, validate holdings against a scenario, flag unsupported positions and driver impacts, and value exposure at the scenario calculation month.
Instructions
Stored portfolios. Actions: list, get, save, delete, check, exposure.
save checks the contract and writes portfolios/<id>.json; check names every
position the scenario's macro and satellite versions cannot serve, with the reason of a
driver the out-of-sample check rejected, and warns what an impact on a macro variable
reaches through the positions' drivers, with the long-run loading of each one (below 0.1
it barely reacts); exposure values the positions at the calculation month of the
scenario's macro version.
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": "portfolio"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | The portfolio id, which is also the name of its file. | |
| spec | No | The portfolio specification save checks against the contract before it writes the file. | |
| action | Yes | What to do: list, get, save, delete, check against a scenario, or value the exposure. save overwrites a portfolio stored under the same id; delete removes the portfolio's file. | |
| scenario | No | The scenario whose macro and satellite versions check and exposure work with. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||