Skip to main content
Glama

skycloak_upgrade_extension

Idempotent

Upgrade an installed extension on a Skycloak cluster to the newest available version. Use it to update extensions asynchronously by passing the cluster ID and extension ID.

Instructions

Upgrade an installed extension to the latest available version. Asynchronous.

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

Input Schema

NameRequiredDescriptionDefault
cluster_idYesthe cluster ID
extension_idYesthe extension ID

Output Schema

NameRequiredDescriptionDefault
sourceYes
statusYes
extension_idYes
extension_nameYes
available_versionNo
installed_versionYes
upgrade_availableYes

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 cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=false), so the description's contribution above that is the 'Asynchronous' disclosure, which is genuinely valuable — it tells the agent the call returns before completion and results must be checked separately. It stops short of saying how to track progress or whether the upgrade disrupts the running extension.

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 sentences, zero filler, and the core action is front-loaded ahead of the asynchronous caveat. Nothing could be trimmed without losing information.

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 two-parameter mutation tool with full schema coverage, complete annotations, and an output schema that documents return values, the description supplies what's needed to call it. The only material gap is that 'Asynchronous' is asserted without any hint of how completion is observed or whether the operation can be cancelled.

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 both required parameters documented inline, so the structured data already carries parameter meaning. The description adds nothing about cluster_id or extension_id semantics, so the baseline of 3 is appropriate.

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 states a specific verb and resource — 'Upgrade an installed extension to the latest available version' — which is more precise than a bare 'upgrade extension' and implies a target version distinct from generic update. It does not, however, explicitly differentiate from close siblings such as skycloak_update_extension, leaving the agent to infer that this is version-bump behavior rather than settings modification.

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: 'installed extension' and 'latest available version' suggest this applies to already-installed extensions wanting a version bump, which weakly separates it from install_extension and update_extension. There are no explicit when-to-use/when-not-to-use statements, no prerequisites (e.g., checking available versions first), and no named alternative.

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