Skip to main content
Glama

skycloak_install_extension

Install a catalog extension on a cluster by providing its ID and required parameters; then poll cluster extensions until the asynchronous status settles.

Instructions

Install a catalog extension on a cluster. Installation is asynchronous; poll skycloak_list_cluster_extensions until the status settles. Provide required parameters keyed by parameter name.

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

Input Schema

NameRequiredDescriptionDefault
cluster_idYesthe cluster ID
parametersNoparameter values keyed by parameter name; required parameters must be provided
extension_idYesthe catalog extension ID to install

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
Behavior3/5

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

The annotations already declare readOnly=false, destructive=false, idempotent=false, and the description adds genuinely new behavioral context by disclosing asynchronous execution and the polling loop required to observe completion. With annotations covering the safety profile, the bar is lower, and the description covers the main non-obvious trait but omits failure/partial-install semantics and permission requirements.

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?

Three short, front-loaded sentences with no filler; the action, the async caveat, and the parameter convention appear in that order. The final sentence largely restates the schema's own description of the parameters object, a small redundancy that keeps it from a 5.

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?

With an output schema present, return values need not be explained, and the async polling guidance plus complete schema coverage cover the essentials. Still missing is what an agent should do if installation fails or how to detect a terminal failure state beyond 'status settles'.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all three parameters and the baseline is 3. The description lightly reinforces parameter semantics by saying required values are keyed by parameter name, which clarifies how to populate the nested parameters object, matching the schema's note.

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, 'Install a catalog extension on a cluster,' and implicitly separates this from the sibling mutations (uninstall/update/upgrade) by naming the install target. It never explicitly names those siblings, so a reader must infer the distinction, which keeps it just short of 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 Guidelines4/5

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

It clearly says the operation is asynchronous and prescribes the follow-up: poll skycloak_list_cluster_extensions until status settles, naming the sibling explicitly. It does not state when to prefer this over update_extension or upgrade_extension, nor any preconditions, so exclusions are absent.

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