Skip to main content
Glama

skycloak_get_cluster_upgrade_path

Read-only

Retrieves the recommended version-upgrade path for a specified cluster, so you can plan each step before upgrading.

Instructions

Get the recommended version-upgrade path for a cluster.

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_upgrade_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_idYesthe cluster ID

Output Schema

NameRequiredDescriptionDefault
stepsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is fully covered and the description is not obligated to repeat it. However, the description adds no behavioral context whatsoever — not what the 'path' contains, whether it is advisory or enforced, nor any prerequisite — so it contributes nothing beyond the annotations and the tool name.

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?

One short sentence, front-loaded with the verb and scope, with no filler or redundancy. Nothing in it could be cut without losing meaning.

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 one well-documented parameter, read-only annotations, and an output schema, the definition covers the mechanics of calling it. It is still thin on what an 'upgrade path' actually is (an ordered list of versions? a single target?) and when in an upgrade workflow it should be consulted.

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% with a single required cluster_id already documented in the schema, so the baseline of 3 applies. The description does not add format details or constraints for cluster_id beyond what the schema states.

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 gives a specific verb ('Get') and a specific resource ('the recommended version-upgrade path for a cluster'), which is meaningfully narrower than siblings like skycloak_list_cluster_upgrades or skycloak_cancel_cluster_upgrade. It does not explicitly name or contrast with those alternatives, so it stops short of full differentiation.

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: nothing says whether to call this before a skycloak_upgrade_extension, how it relates to skycloak_list_cluster_upgrades, or whether an upgrade must be in a particular state. The agent must infer the planning use case from the word 'recommended' alone.

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