Skip to main content
Glama

skycloak_remove_realm_user_from_group

DestructiveIdempotent

Removes a user from a Keycloak realm group in a managed cluster by specifying the cluster, realm, user, and group IDs.

Instructions

Remove a user from a realm group.

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>",
      "group_id": "<group_id>"
    },
    "name": "skycloak_remove_realm_user_from_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
realmYesthe Keycloak realm name
user_idYesthe user ID
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

C2.9/5.0
Behavior2/5

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

The annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that: it does not say what happens when the user is not a member, whether the call errors or is a no-op, or whether group-derived role mappings are affected.

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?

A single front-loaded sentence with zero filler and no redundancy. It is efficient, though the brevity reflects under-specification rather than disciplined editing.

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 and annotations fully describe the mutation's risk and idempotency, so the description need not explain return values. However, for a destructive membership mutation, the description leaves out edge-case behavior that an agent would need before invoking it, making it only minimally complete.

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 (cluster_id, realm, user_id, group_id) are already documented in the schema. The description contributes no additional meaning about identifier formats or scoping, which is the expected baseline when the schema does the heavy lifting.

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 ('Remove a user from a realm group'), which is unambiguous and implicitly contrasts with the add_realm_user_to_group sibling. It does not explicitly name or differentiate against any sibling, so it stops short of 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 Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites such as the user needing to be a current member, and no reference to alternatives like skycloak_remove_realm_user_role or skycloak_add_realm_user_to_group. The agent must infer the usage context entirely from the name.

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