Apply an approved schedule
apply_scheduleCreate calendar events for an approved plan using its plan_id, first returning a confirmation token and summary; resubmit the token after user approval to write events while skipping newly busy times.
Instructions
Create calendar events for a plan the user has approved. Requires a plan_id from propose_schedule. The first call returns a confirm_token and a summary of exactly what will be created; call again with the token only after the user has said yes. Busy time is re-checked immediately before writing, so anything that became busy since the proposal is skipped rather than double-booked.
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_id": "<plan_id>"
},
"name": "apply_schedule"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| account | No | Account to create the events on. Required when more than one account is eligible. | |
| plan_id | Yes | The plan_id returned by propose_schedule. | |
| calendar | No | Calendar id on that account. Defaults to its default calendar. | |
| confirm_token | No | Confirmation token returned by a previous CONFIRMATION_REQUIRED response. Only supply this after the user has explicitly approved the exact action described. | |
| skip_activities | No | Activity ids the user declined, e.g. ["part-time"]. Everything else is created. |