Skip to main content
Glama

skycloak_cancel_cluster_upgrade

Destructive

Cancel an in-progress Skycloak cluster version upgrade by providing the cluster ID and setting confirm=true to authorize the cancellation.

Instructions

Cancel an in-progress cluster version upgrade. 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_cancel_cluster_upgrade"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesmust be true to confirm cancellation
cluster_idYesthe cluster ID

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, so the safety profile is known. The description adds the confirm-gate requirement, which is useful behavioral context, but omits the genuinely valuable details: what happens to a partially applied upgrade, whether it rolls back, and whether the cluster is left in a degraded state.

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, the action first and the confirmation guard second. Nothing redundant and nothing buried.

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?

With an output schema present and full schema coverage, the description need not explain return values, and it covers the action and the confirmation requirement. For a destructive mutation on a live cluster, however, it should say what state the cluster ends up in after cancellation.

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?

Both parameters are already documented at 100% schema coverage, including the requirement that confirm be true, so the description's 'Set confirm=true' merely repeats the schema. No additional meaning (format of cluster_id, reset behavior of confirm on retry) is added.

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?

A specific verb (cancel) plus a specific resource (an in-progress cluster version upgrade) tells the agent exactly what the tool does, and the qualifier 'in-progress' implicitly separates it from upgrade-path or listing tools like get_cluster_upgrade_path. It stops short of explicitly naming a sibling to route away from.

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?

The phrase 'in-progress cluster version upgrade' implies the condition under which the tool applies, but the description never states what to do first (e.g., verify with list_cluster_upgrades) or what alternative applies if the upgrade is not actually running. Usage is inferable rather than 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