Skip to main content
Glama

skycloak_set_cluster_maintenance_window

Idempotent

Create or replace a cluster-specific maintenance window with enabled status, weekly days, local start/end times, and timezone to control when maintenance runs.

Instructions

Create or replace a cluster-specific maintenance window.

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>",
      "enabled": "<enabled>",
      "days_of_week": "<days_of_week>",
      "start_local": "<start_local>",
      "end_local": "<end_local>",
      "timezone": "<timezone>"
    },
    "name": "skycloak_set_cluster_maintenance_window"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYeswhether the window is active
timezoneYesIANA timezone, e.g. Europe/Berlin
end_localYeslocal end time in HH:MM format
cluster_idYesthe cluster ID
start_localYeslocal start time in HH:MM format
days_of_weekYesdays of week, 0=Sunday through 6=Saturday

Output Schema

NameRequiredDescriptionDefault
enabledYes
timezoneYes
end_localYes
start_localYes
days_of_weekYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false. The phrase 'create or replace' usefully corroborates the idempotent upsert behavior and warns that an existing window is overwritten, but the description never says what the previous window configuration loses, whether disabling requires enabled=false versus deletion, or what permissions are needed. Modest added value on top of a well-annotated tool.

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

Conciseness4/5

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

A single front-loaded sentence with no filler, and the upsert semantics sit in the verb position where they are most useful. It is arguably too terse rather than padded, so there is no waste to trim.

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

Completeness3/5

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

An output schema exists, so return values need not be described, and annotations cover the safety profile. However, for a six-required-parameter upsert that replaces existing configuration, the description omits replacement consequences, validity constraints on the time range, and permission requirements, leaving it only minimally adequate.

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% (cluster_id, enabled, timezone, start_local, end_local, days_of_week all documented), so the schema carries parameter meaning and the baseline is 3. The description adds nothing about the required HH:MM local-time pairing, the 0=Sunday indexing, or how timezone interacts with local times.

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

Purpose4/5

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

The description names a specific verb pair and resource: 'Create or replace a cluster-specific maintenance window.' That clearly separates it from the read/delete siblings (skycloak_get_cluster_maintenance_window, skycloak_delete_cluster_maintenance_window) and the 'replace' wording signals upsert semantics rather than a plain create. It does not name the sibling alternatives explicitly, which keeps it from a 5.

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

Usage Guidelines2/5

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

There is no when-to-use guidance: no statement of prerequisites (existing cluster, permissions), no condition distinguishing a fresh set from a replacement, and no pointer to the get/delete siblings for the other maintenance-window operations. An agent can infer from the name that this configures a window, but nothing in the text routes it among alternatives.

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