Skip to main content
Glama
Sign In
mcp-keycloak

mcp-keycloak

by idoyudha
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

remove_realm_role_from_user

Remove realm roles from a user in Keycloak. Provide user ID and role names to revoke access.

Instructions

Remove realm roles from a user.

Args:
    user_id: User ID
    role_names: List of role names to remove
    realm: Target realm (uses default if not specified)

Returns:
    Status message

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": {
      "user_id": "<user_id>",
      "role_names": "<role_names>"
    },
    "name": "remove_realm_role_from_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYes
role_namesYes
realmNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It only states the action and vague return type, omitting details about permissions, reversibility, side effects (e.g., session impact), or error cases.

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?

The description is extremely concise, using a single introductory sentence followed by a structured list of arguments and return value. Every element serves a purpose with no redundancy.

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 description covers basic functionality and parameter roles, but lacks details on realm role semantics, required user membership, error handling, or the structure of the returned 'Status message'. Despite an output schema existing, the description alone is not fully self-contained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage, so the description must compensate. It provides brief but clear meanings for each parameter: user_id as 'User ID', role_names as 'List of role names to remove', and realm as 'Target realm (uses default if not specified)'. This adds value over the schema's bare titles.

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 uses a specific verb 'remove' with a clear resource 'realm roles from a user'. It directly states the function's purpose and differentiates it from sibling tools like 'assign_realm_role_to_user', which performs the opposite operation.

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?

The description provides no explicit guidance on when to use or not use this tool. It does not mention alternatives or prerequisites, leaving the agent to infer usage solely from the action description.

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