Skip to main content
Glama

skycloak_remove_realm_user_role

DestructiveIdempotent

Remove a realm role from a specified Keycloak user in a Skycloak cluster by providing the cluster ID, realm, user ID, and role name.

Instructions

Remove a realm role from a user.

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>",
      "role_name": "<role_name>"
    },
    "name": "skycloak_remove_realm_user_role"
  }
}

Input Schema

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

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 doesn't say whether the role assignment is silently a no-op if absent, whether errors occur for unknown realms/users, or what permissions are needed.

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 no filler or redundancy. It is as terse as possible, though that terseness comes at the cost of any routing or behavioral information.

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 cover the destructive/idempotent profile, so the description needn't explain return values or safety. Still, for a destructive disassociation tool among many similar role/group tools, the absence of any disambiguation from assign_realm_user_role or remove_application_role leaves a genuine 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 description coverage is 100%, with all four required parameters (cluster_id, realm, user_id, role_name) documented in the schema itself. The description adds no extra meaning such as identifier formats or whether role_name is case-sensitive, so the baseline of 3 applies.

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 gives a specific verb ('Remove') and a specific resource ('a realm role from a user'), which is unambiguous about the operation. It does not explicitly name the counterpart sibling (assign_realm_user_role) or distinguish realm roles from application roles, so it stops short of full sibling differentiation.

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 prerequisites, and no mention of alternatives such as removing an application role or removing the user from a group. The agent must infer the selection context purely from the tool 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