Skip to main content
Glama

skycloak_delete_realm_group

Destructive

Deletes a realm group in a Keycloak realm and requires confirm=true to proceed. Use it to remove a specific group by cluster, realm, and group ID.

Instructions

Delete a realm group. 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>",
      "realm": "<realm>",
      "group_id": "<group_id>",
      "confirm": "<confirm>"
    },
    "name": "skycloak_delete_realm_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
realmYesthe Keycloak realm name
confirmYesmust be true to confirm deletion
group_idYesthe group ID
cluster_idYesthe cluster ID

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 and idempotentHint=false, so the safety profile is largely covered structurally. The description adds the useful confirm-gate behavior, but omits whether member assignments are cascaded away, whether the group must be empty first, and whether the call fails on a nonexistent group.

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, front-loaded with the action and followed immediately by the blocking precondition. There is no redundant or filler wording.

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?

With a full schema, an output schema, and destructive annotations, the description does not need to explain return values or safety flags. However, for a destructive operation it is thin on consequences — cascade behavior on group memberships and failure conditions go unmentioned.

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%, so all four parameters are already documented in structured form and the baseline applies. The description's mention of confirm=true restates the schema's own 'must be true to confirm deletion' without adding format or interaction detail.

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 ('Delete a realm group'), which distinguishes it from sibling reads and updates such as skycloak_get_realm_group or skycloak_update_realm_group by name. It does not explicitly note that this is scoped to a group inside a specific realm versus skycloak_delete_realm, though the wording makes that reasonably evident.

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?

It gives one concrete precondition ('Set confirm=true to proceed'), which tells the agent how to successfully invoke the tool. It offers no guidance on when deletion is appropriate versus alternatives like removing individual members, and no warning about the point of no return.

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