Save a strategy
strategy_saveCreates a crypto trading strategy or saves a new revision so dry-runs and backtests have a saved strategy ID; updates only version when the config changes.
Instructions
Creates a strategy (no strategyId) or saves a new revision of an existing one (strategyId). Dry-runs and backtests need a saved strategy id; a PUT only bumps the version when the config structurally changed. name and description replace the stored ones. visibility: a new strategy is PRIVATE unless you pass PUBLIC. An update never changes visibility (that is strategy_set_visibility, on the user's explicit request only); saving into a PUBLIC strategy publishes the new config to every user, so it is refused unless you pass visibility:"PUBLIC" to confirm, and a visibility that differs from the stored one is refused. Nothing is saved when refused.
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": {
"name": "<name>",
"config": "<config>"
},
"name": "strategy_save"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| config | Yes | ||
| strategyId | No | ||
| visibility | No | Create: default PRIVATE. Update: must match the stored visibility when given; required as "PUBLIC" to save into a PUBLIC strategy. | |
| description | No |