Skip to main content
Glama

skycloak_delete_cluster

Destructive

Permanently delete a Keycloak cluster and all its realms and data. Set confirm=true to proceed with this irreversible removal.

Instructions

Permanently delete a Keycloak cluster and all of its realms and data. Irreversible. 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": {
      "id": "<id>",
      "confirm": "<confirm>"
    },
    "name": "skycloak_delete_cluster"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe cluster ID to delete
confirmYesmust be true to confirm permanent, irreversible deletion of the cluster and all its data

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/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 genuinely useful detail beyond them by disclosing the cascade effect (realms and all data are destroyed) and the confirm=true guard requirement. It stops short of noting permission requirements, rate limits, or whether deletion is asynchronous, which keeps it from a 5.

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 compact sentences with the irreversible consequence front-loaded right after the action; every sentence carries information, though 'Permanently' and 'Irreversible' are partially redundant.

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 destructive two-parameter mutation with rich annotations and an output schema, the definition covers the essentials: what is destroyed, that it cannot be undone, and the confirmation gate. Minor gaps like permission requirements or post-deletion state are acceptable given annotation coverage.

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 both id and confirm are documented in the schema itself; the description's mention of confirm=true restates rather than extends that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb (permanently delete) and resource (a Keycloak cluster), and the scope clause 'all of its realms and data' distinguishes a whole-cluster deletion from sibling tools that delete individual realms, users, roles or applications.

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?

'Irreversible' and the required confirm=true flag implicitly signal that this is a last-resort, high-caution operation, but the description never states when to choose this tool over skycloak_delete_realm or other sibling deletes, nor any preconditions such as ownership or cluster state.

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