Skip to main content
Glama

skycloak_get_cluster_maintenance_window

Read-only

Retrieve a cluster-specific maintenance window; if none exists, the response indicates the cluster uses the workspace default.

Instructions

Get a cluster-specific maintenance window. A 404 means the cluster follows the workspace default.

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

Input Schema

NameRequiredDescriptionDefault
cluster_idYesthe cluster ID

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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely non-obvious behavioral context beyond the annotations: a 404 is not an error but an indicator that the cluster inherits the workspace default, which changes how an agent should branch on the response.

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 short sentences, front-loaded with the purpose and followed by the one edge case that matters. Nothing is redundant and nothing needs pruning.

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?

An output schema exists, so return values need not be described, and the 404 fallback behavior — the main trap for this call — is covered. Minor gap: it does not say whether the workspace default window is retrievable elsewhere when a 404 occurs, leaving the agent's next step unspecified.

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% for the single cluster_id parameter, so the schema carries the parameter documentation. The description adds only the word "cluster-specific" and no format or sourcing details for the ID, so baseline 3 applies.

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 and resource ("Get a cluster-specific maintenance window") and its scoping (cluster-specific, implying a workspace-level counterpart). It is clearly distinguishable from the set/delete maintenance-window siblings by the verb, though it does not explicitly 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 Guidelines3/5

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

Usage is only implied: an agent can infer this is the read path for a cluster's maintenance window, but the description never says when to prefer it over the workspace default or over skycloak_set_cluster_maintenance_window / skycloak_delete_cluster_maintenance_window. No exclusions or prerequisites are stated.

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