Skip to main content
Glama

skycloak_uninstall_extension

Destructive

Uninstall an extension from a Skycloak cluster by specifying the cluster ID and extension ID; set confirm=true to proceed.

Instructions

Uninstall an extension from a cluster. Set confirm=true to proceed.

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>",
      "confirm": "<confirm>"
    },
    "name": "skycloak_uninstall_extension"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesmust be true to confirm uninstall
cluster_idYesthe cluster ID
extension_idYesthe extension ID to uninstall

Output Schema

NameRequiredDescriptionDefault

No arguments

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 destructiveHint=true, readOnlyHint=false, idempotentHint=false and openWorldHint=false, so the danger profile is fully covered structurally. The description restates the confirm gate but adds nothing about what is lost on uninstall (configuration, stored data), whether the action is reversible, or whether it takes effect immediately.

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 short sentences, no filler, and the destructive prerequisite is placed where it will be read before invocation. Nothing could be removed without losing content.

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?

An output schema exists, so return values need no explanation, and the three parameters are documented. For a destructive mutation, though, the definition should say whether uninstalling wipes extension state or can be undone, and it is silent on that.

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% and all three required parameters carry their own descriptions, including the confirm gate. The description's 'Set confirm=true' merely echoes the schema's 'must be true to confirm uninstall,' adding no format, constraint, or identifier-lookup detail beyond structured data.

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?

Specific verb plus resource plus scope: 'Uninstall an extension from a cluster,' which is more precise than the name alone. It does not, however, distinguish itself from the closely named siblings skycloak_delete_extension, skycloak_update_extension or skycloak_upgrade_extension, so an agent must guess whether 'uninstall' and 'delete' differ.

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?

The only guidance is the procedural prerequisite 'Set confirm=true to proceed,' which tells the agent how to execute but not when to prefer this over skycloak_delete_extension or skycloak_upgrade_extension. Usage context is implied by the verb rather than stated, and no exclusions are given.

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