Skip to main content
Glama

skycloak_delete_realm_user

Destructive

Deletes a user from a Keycloak realm in a Skycloak cluster; requires cluster ID, realm, user ID, and confirm=true. Use it to remove realm users safely.

Instructions

Delete a realm user. 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>",
      "user_id": "<user_id>",
      "confirm": "<confirm>"
    },
    "name": "skycloak_delete_realm_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
realmYesthe Keycloak realm name
confirmYesmust be true to confirm deletion
user_idYesthe user ID
cluster_idYesthe cluster ID

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered structurally. The description adds the useful confirm-gate requirement, but says nothing about cascade effects (group memberships, role mappings, sessions/credentials also lost) or that the operation cannot be undone.

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, front-loaded with the action and immediately followed by the required gate. No filler; the only shortfall is that nothing else of substance follows.

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?

The tool is simple (4 required flat params, full schema coverage, output schema present), and annotations carry the destructive contract, so the description is minimally sufficient to call it. It is not sufficient to predict consequences of calling it, which matters for an irreversible delete.

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%, so cluster_id, realm, user_id, and confirm are all documented in the schema, including that confirm "must be true to confirm deletion." The description merely restates the confirm requirement rather than adding format, identity, or lookup guidance beyond the schema.

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?

"Delete a realm user" names a specific verb and resource, and the resource is distinct enough (realm user vs. realm, realm group, realm role) that an agent can tell it apart from the delete siblings. It stops short of explicitly contrasting with siblings such as skycloak_delete_realm or skycloak_remove_realm_user_from_group, which would earn 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 Guidelines3/5

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

The description gives one concrete precondition (confirm=true) but no guidance on when this tool is appropriate versus alternatives, nor any warning that it is irreversible rather than a membership/role removal. Usage is implied by the name, not explained.

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