Skip to main content
Glama

skycloak_list_cluster_extensions

Read-only

Lists extensions installed on a cluster and compares installed vs. available versions for the cluster's Keycloak, including upgrade status.

Instructions

List the extensions currently installed on a cluster, with their installed version, the version available for the cluster's Keycloak, and upgrade status.

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

Input Schema

NameRequiredDescriptionDefault
cluster_idYesthe cluster ID

Output Schema

NameRequiredDescriptionDefault
countYes
extensionsYes

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 declare readOnlyHint=true, openWorldHint=false and idempotentHint=false, so the safety profile is covered structurally. The description adds genuine value by stating exactly what is reported (installed version, version available for the cluster's Keycloak, upgrade status), but says nothing about permissions, scoping, or behavior when no Keycloak version is set.

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 well-formed sentence with the resource front-loaded and the returned fields trailing; every clause carries information. Slightly overpacked with three return fields in a single sentence, but nothing is wasteful.

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?

For a simple single-parameter read tool with annotations and an output schema, the description covers purpose and returned content adequately. The only real gap is the lack of routing guidance among the many sibling list_* tools, which is a minor omission given the explicit 'installed on a cluster' scoping.

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?

There is a single required parameter with 100% schema description coverage, so the baseline is 3. The description's 'on a cluster' loosely corresponds to cluster_id but adds no meaning beyond the schema, such as accepted ID format or where to obtain the ID.

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 (List) and resource (extensions installed on a cluster) and enumerates the returned fields, so an agent can distinguish this from the sibling skycloak_list_extensions (which by name alone suggests a catalog of available extensions). It stops short of explicitly contrasting the two, 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 Guidelines3/5

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

Usage is only implied: 'currently installed on a cluster' tells the agent this is the per-cluster installed view, so an agent can infer when to call it. There is no explicit when-to-use/when-not statement and no named alternative such as skycloak_list_extensions or skycloak_list_cluster_upgrades.

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