Skip to main content
Glama

Delete power schedule

delete_power_schedule
Destructive

Delete a power schedule from a cluster: the schedule stops firing immediately and disappears from the cluster's schedule list. The cluster itself is not touched - a stop or start the schedule already performed is not undone, and deleting is reversible in effect (create_power_schedule recreates the same schedule). To pause a schedule while keeping its configuration, prefer update_power_schedule with enabled false. Get the schedule_id from list_power_schedules.

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>"
    },
    "name": "delete_power_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_idNoUUID of the target cluster. Optional when a cluster is selected.
schedule_idYesUUID of the schedule to delete, from list_power_schedules.
cluster_nameNoExact name of the target cluster. Optional when a cluster is selected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say destructiveHint=true and idempotentHint=false; the description goes well beyond that by stating the schedule stops firing immediately, the cluster itself is untouched, a previously executed stop/start is not undone, and the effect can be recreated via create_power_schedule. That is exactly the blast-radius information an agent needs before a destructive call, and it does not conflict with the annotation profile.

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

Conciseness5/5

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

Three tight sentences, front-loaded with the delete action and its immediate effect, then the safety caveats, then the alternative and ID source. No filler, and each sentence carries distinct decision-relevant information.

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?

With no output schema, the description appropriately covers consequences and side effects, and annotations already carry the destructive/idempotency profile. The only minor gap is that it does not state what the call returns or how failures (e.g., unknown schedule_id) surface, which is a small omission for a delete tool.

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?

Schema coverage is 100%, so the schema already documents cluster_id, cluster_name, and schedule_id, including that cluster identifiers are optional when a cluster is selected. The description only restates that schedule_id comes from list_power_schedules, adding no syntax or meaning beyond the schema, so the baseline 3 applies.

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 description opens with a specific verb and resource ('Delete a power schedule from a cluster') and immediately scopes the effect ('stops firing immediately and disappears from the cluster's schedule list'), so an agent can tell this apart from delete_cluster or update_power_schedule without inspecting any schema.

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?

It names the alternative explicitly ('To pause a schedule while keeping its configuration, prefer update_power_schedule with enabled false') and gives the condition that selects it, plus the prerequisite for obtaining schedule_id via list_power_schedules. Both the when-to-use and the when-to-use-something-else cases are covered.

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.