Skip to main content
Glama

skycloak_list_cluster_versions

Read-only

Lists the Keycloak or Tidecloak versions available for a given cluster type, helping you select a compatible version before deployment.

Instructions

List the Keycloak versions available for a cluster type.

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": {
      "type": "<type>"
    },
    "name": "skycloak_list_cluster_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYescluster type: keycloak or tidecloak (case-insensitive)

Output Schema

NameRequiredDescriptionDefault
versionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 covered structurally. The description adds nothing beyond that: no note on what the version list represents (selectable install versions vs. upgrade targets), no pagination, and it does not address the curious idempotentHint=false for what should be a stable read.

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?

One short, front-loaded sentence with no padding. It is efficient, though it is arguably too terse given the tool's relational context to the upgrade-path tools.

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 and full annotation coverage, most of what an agent needs is elsewhere. Still, the description leaves the 'Keycloak vs tidecloak' scope mismatch and the relationship to upgrade-path tooling unresolved, which matters for a lookup tool with many near-named siblings.

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 coverage is 100% and the single parameter already documents the accepted values and case-insensitivity. The description only restates 'for a cluster type' and adds no new meaning, so the baseline of 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 uses a specific verb ('List') and resource ('Keycloak versions available for a cluster type'), which is enough to separate it from siblings like skycloak_list_cluster_types or skycloak_list_cluster_upgrades. Minor ambiguity: it says 'Keycloak versions' while the parameter also accepts 'tidecloak', so the resource scope is slightly narrower than the schema allows.

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 and no mention of alternatives such as get_cluster_upgrade_path or list_cluster_upgrades, which sound related. The agent must infer from the name alone when this lookup is the right one.

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