Skip to main content
Glama

Update power schedule

update_power_schedule
Destructive

Replace a power schedule's action, timing, and enabled flag, and re-arm its next run. This is a FULL REPLACE, not a patch: restate every field of the schedule as it should be afterwards - enabled must always be passed (an omitted enabled is refused rather than silently re-enabling a paused schedule), and a 'cron' schedule must restate its timezone (an omitted timezone is refused rather than silently shifting the fire hour to UTC). Call list_power_schedules first for the schedule_id and the current values. Passing enabled false pauses the schedule without losing its configuration; true re-arms it for its next occurrence. The same VM-termination caution and stop_mode semantics as create_power_schedule apply to stop schedules ('delete_resources' terminates every VM; 'scale_to_zero' deletes the worker servers, losing data on their own disks, and keeps the control plane running). A 'stop' schedule must also restate its stop_mode (an omitted stop_mode is refused rather than silently reverting a scale-to-zero schedule to the destructive default). An enabled scale_to_zero stop on a cluster whose inventory shows claims on a worker's own disk is refused unless accept_node_local_data_loss is true, which may only be set after the user has explicitly agreed to lose that data at every stop, exactly as for create_power_schedule. Do not use it to turn a schedule into an off-hours saving schedule; propose_off_hours_schedule files that decision.

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": {
      "schedule_id": "<schedule_id>",
      "action": "<action>",
      "schedule_kind": "<schedule_kind>",
      "enabled": "<enabled>"
    },
    "name": "update_power_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesWhat the schedule does when it fires.
run_atNoRFC 3339 timestamp of the single fire, e.g. '2026-01-02T19:00:00Z'. Required for schedule_kind 'once'; must be in the future.
enabledYesWhether the schedule is armed. Must always be passed on update: false pauses the schedule, true (re-)arms it.
timezoneNoIANA timezone the cron expression is evaluated in, e.g. 'Europe/Stockholm'. Must be restated for 'cron' schedules.
stop_modeNoHow a stop fires: 'delete_resources' (default) is the full stop_cluster teardown that terminates every VM; 'scale_to_zero' deletes the worker servers (data on their own disks is lost at every stop) and keeps the control plane, networks, SSH keys and cloud volumes; 'pause' powers every server off and keeps it with its disks (etcd and local data survive) - k3s clusters on Hetzner, UpCloud and DigitalOcean only, and what a stop always does on AWS, Scaleway and Ankra Cloud. A pause saves no compute cost on Hetzner, DigitalOcean or UpCloud (Developer and General Purpose plans): they bill a powered-off server at its full price, so say so and offer scale_to_zero or delete_resources when the user wants to save. On AWS and Scaleway a powered-off server stops billing compute; its disks and IPs keep billing. Only meaningful with action 'stop'.
cluster_idNoUUID of the target cluster. Optional when a cluster is selected.
schedule_idYesUUID of the schedule to replace, from list_power_schedules.
cluster_nameNoExact name of the target cluster. Optional when a cluster is selected.
schedule_kindYes'once' fires a single time at run_at; 'cron' fires repeatedly per cron_expression.
preserve_stateNoFor a 'stop' schedule with stop_mode 'delete_resources' on a provider whose stop deletes the VMs: capture the cluster's state (an encrypted etcd snapshot) before the teardown, and restore it on the next start. When the capture cannot run, the stop is refused and nothing is torn down; the failure says to set preserve_state false to allow a stop without saving state. Defaults to true on create, so the stop captures state unless you pass false; on update an omitted value keeps the schedule's current setting. Ignored for other schedules.
cron_expressionNoStandard 5-field cron expression, e.g. '0 19 * * 1-5'. Required for schedule_kind 'cron'. Must not embed a timezone; use the timezone parameter.
accept_node_local_data_lossNoThe user's explicit consent to losing the data on the worker disks at every stop of an enabled scale_to_zero stop schedule. On a cluster whose inventory shows persistent volume claims on a worker's own disk, such a schedule is refused without it and the refusal names the claims. Set it to true ONLY after you have shown the user those claims and the user has explicitly agreed to lose that data - never on your own judgement, never pre-emptively, and not because the user asked for the schedule. Ignored for every other schedule; defaults to false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / stop_mode / description
      Previous value: -"How a stop fires: 'delete_resources' (default) is the full stop_cluster teardown that terminates every VM; 'scale_to_zero' deletes the worker servers (data on their own disks is lost at every stop) and keeps the control plane, networks, SSH keys and cloud volumes; 'pause' powers every server off and keeps it with its disks (etcd and local data survive) - k3s clusters on Hetzner, UpCloud and DigitalOcean only, and what a stop always does on AWS and Scaleway. A pause saves no compute cost on Hetzner, DigitalOcean or UpCloud (Developer and General Purpose plans): they bill a powered-off server at its full price, so say so and offer scale_to_zero or delete_resources when the user wants to save. On AWS and Scaleway a powered-off server stops billing compute; its disks and IPs keep billing. Only meaningful with action 'stop'."New value: +"How a stop fires: 'delete_resources' (default) is the full stop_cluster teardown that terminates every VM; 'scale_to_zero' deletes the worker servers (data on their own disks is lost at every stop) and keeps the control plane, networks, SSH keys and cloud volumes; 'pause' powers every server off and keeps it with its disks (etcd and local data survive) - k3s clusters on Hetzner, UpCloud and DigitalOcean only, and what a stop always does on AWS, Scaleway and Ankra Cloud. A pause saves no compute cost on Hetzner, DigitalOcean or UpCloud (Developer and General Purpose plans): they bill a powered-off server at its full price, so say so and offer scale_to_zero or delete_resources when the user wants to save. On AWS and Scaleway a powered-off server stops billing compute; its disks and IPs keep billing. Only meaningful with action 'stop'."
  2. Changed1 schema field changed
    • changedInput schema / properties / preserve_state / description
      Previous value: -"For a 'stop' schedule with stop_mode 'delete_resources' on a provider whose stop deletes the VMs: capture the cluster's state (an encrypted etcd snapshot) before the teardown, and restore it on the next start. When the capture cannot run, the stop is refused and nothing is torn down; the failure says to set preserve_state false to allow a stop without saving state. Defaults to false on create; on update an omitted value keeps the schedule's current setting. Ignored for other schedules."New value: +"For a 'stop' schedule with stop_mode 'delete_resources' on a provider whose stop deletes the VMs: capture the cluster's state (an encrypted etcd snapshot) before the teardown, and restore it on the next start. When the capture cannot run, the stop is refused and nothing is torn down; the failure says to set preserve_state false to allow a stop without saving state. Defaults to true on create, so the stop captures state unless you pass false; on update an omitted value keeps the schedule's current setting. Ignored for other schedules."
  3. First observed

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, but the description adds a lot beyond them: omitted fields are refused rather than silently defaulted, stop_mode 'delete_resources' terminates every VM, 'scale_to_zero' loses worker-local disk data, and a data-loss-bearing schedule is refused without explicit user consent. The only gap is the return/response shape, which has no output schema to cover it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The full-replace constraint and the list_power_schedules prerequisite are front-loaded, which is correct, but the single dense paragraph re-explains stop_mode enum semantics ('delete_resources' terminates every VM, 'scale_to_zero' loses worker-disk data) that the schema already spells out at length. Useful content is padded with duplication and one trailing exclusions sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, 12-parameter mutation tool with no output schema, the definition covers prerequisites, refusal behavior on omitted fields, destructive outcomes, cost implications of pause, and the consent protocol. What remains unstated is only the response/pagination shape, which is minor given the annotations carry the safety profile.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage the schema already documents all 12 parameters, including per-parameter consent rules for accept_node_local_data_loss and the create-vs-update default difference for preserve_state. The description's main added value is cross-parameter rules (cron must restate timezone, stop must restate stop_mode, enabled always required), so it goes modestly beyond the schema but largely reinforces it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence states a specific verb+resource (replace a power schedule's action, timing, enabled flag) and explicitly frames it as a FULL REPLACE, which distinguishes it from create_power_schedule and from any patch-style sibling. It also names the sibling it must not be used for (propose_off_hours_schedule).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing: call list_power_schedules first to obtain schedule_id and current values; do not use this to convert a schedule into an off-hours saving schedule, use propose_off_hours_schedule instead. It also states the refusal conditions (enabled false pauses without losing config, true re-arms) and the consent precondition for accept_node_local_data_loss.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.