Save plan
save_planSaves the plan on the server, only if the user asked to save it. Without user_code it creates a new personal code and returns it — show the code to the user and ask them to write it down: with it they can open their plans in any chat. Nobody else needs the code and it cannot be recovered.
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": {
"plan": "<plan>"
},
"name": "save_plan"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| plan | Yes | The same object you pass to show_renovation_plan (title, locale, currency, mode, stages, materials, notes…) | |
| plan_id | No | If you are updating an already saved plan | |
| view_id | No | view_id of the shown plan — then line edits and checklist ticks are saved too, and the open plan remembers the code | |
| user_code | No | User's personal code if they already have one, e.g. oak-river-moon-4821 |