Skip to main content
Glama

skycloak_delete_extension

Destructive

Deletes a custom extension from the Skycloak workspace catalog; requires extension_id and confirm=true to prevent accidental removal.

Instructions

Delete a custom extension from the workspace catalog. 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": {
      "extension_id": "<extension_id>",
      "confirm": "<confirm>"
    },
    "name": "skycloak_delete_extension"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesmust be true to confirm deletion
extension_idYesthe extension ID

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is covered. The description adds that removal is scoped to the workspace catalog, implying it does not touch installed instances, but it does not state irreversibility or what happens to dependent installs.

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?

Two short sentences with the action and scope front-loaded; nothing is padded. The second sentence is largely redundant with the schema but functions as a safety reminder, which is a minor, forgivable overlap.

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 confirm gate is covered. For a destructive, non-idempotent operation whose name collides with a sibling uninstall tool, the missing disambiguation is a real completeness gap.

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%, with both parameters self-documented, so the baseline is 3. The sentence 'Set confirm=true to proceed' merely restates the schema's confirm description rather than adding new meaning.

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?

States a specific verb and resource: 'Delete a custom extension from the workspace catalog.' The catalog scoping narrows it usefully, but it never distinguishes deletion from the closely named sibling skycloak_uninstall_extension, leaving the agent to guess which removes the catalog entry versus the installed artifact.

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?

The only guidance is 'Set confirm=true to proceed,' which is a mechanical precondition rather than when-to-use guidance. Nothing says when to pick this over uninstall, upgrade, or update for the same extension.

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