Skip to main content
Glama
Sign In
keycloak-mcp-server

keycloak-mcp-server

by thebylito
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

remove-role-from-group

Remove a role from a group in Keycloak: provide realm, groupId, roleName, and optionally clientId to target a client role.

Instructions

Remove a realm role, or a client role when clientId is given, from a 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": {
      "realm": "<realm>",
      "groupId": "<groupId>",
      "roleName": "<roleName>"
    },
    "name": "remove-role-from-group"
  }
}

Input Schema

NameRequiredDescriptionDefault
realmYesRealm name
groupIdYesGroup ID
clientIdNoClient ID to resolve roleName as a client role. Omit for a realm role
roleNameYesRole name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.2/5.0
Behavior3/5

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

As a mutation tool with no annotations, the description does not disclose permissions, reversibility, or failure behavior. It does clarify that removal targets a specific role type (realm or client based on clientId), but lacks deeper side-effect information.

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?

Single sentence, front-loaded with the action, no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple removal operation, the description covers the essential behavior and the key conditional parameter. It could mention that the role assignment is removed without deleting the role itself, but the wording implies this.

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 coverage is 100%, and the description adds meaning beyond the schema by explaining when to omit clientId for realm roles and that clientId resolves roleName as a client role.

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') and resource ('group'), clearly states the scope (realm role vs client role via clientId), and distinguishes from sibling tools like remove-role-from-user and assign-role-to-group.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It provides clear context on when to use (removing a role from a group) and how to choose between realm and client roles via clientId. No explicit alternatives are named, but sibling tool names make the distinction.

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