Skip to main content
Glama

skycloak_delete_cluster_maintenance_window

Destructive

Deletes a cluster-specific maintenance window so the cluster reverts to the workspace default. Set confirm=true to proceed.

Instructions

Delete a cluster-specific maintenance window so the cluster follows the workspace default. Set confirm=true to proceed.

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": {
      "cluster_id": "<cluster_id>",
      "confirm": "<confirm>"
    },
    "name": "skycloak_delete_cluster_maintenance_window"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesmust be true to confirm deletion
cluster_idYesthe cluster ID

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description adds real value by stating the post-delete state (falls back to workspace default) and reinforcing the confirm=true guard, though it does not say what happens if no cluster-specific window exists or whether a second delete errors.

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?

Two sentences totaling one clause each, with the outcome/effect front-loaded before the confirmation requirement. Nothing is redundant or padded.

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 two-parameter destructive tool with full schema coverage, existing annotations, and an output schema that handles return values, this is nearly complete. It only omits edge-case behavior (no existing override, permission requirements), which are minor for a call this narrow.

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 description coverage is 100%, so the baseline is 3. 'Set confirm=true to proceed' restates the intent already in the schema's confirm description, and cluster_id is left to the schema entirely, so the description adds no syntax or constraint detail beyond structured fields.

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?

States a specific verb (Delete) and a precisely scoped resource (a cluster-specific maintenance window), and adds the resulting state — the cluster reverts to the workspace default. That outcome framing cleanly separates it from set_cluster_maintenance_window and get_cluster_maintenance_window without needing to name them.

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

Usage Guidelines4/5

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

The clause 'so the cluster follows the workspace default' tells an agent exactly when this is the right call: only when a cluster-specific override exists and should be removed. It does not explicitly warn when not to use it or name the set_/get_ siblings as alternatives, so a small inference step remains.

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

Deploy Server

Other Tools