keycloak-mcp-server

remove-organization-member

Removes a specified user from an organization in Keycloak using the realm, organization ID, and user ID.

Instructions

Remove a user from an organization

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>",
      "orgId": "<orgId>",
      "userId": "<userId>"
    },
    "name": "remove-organization-member"
  }
}

Input Schema

Name	Required	Description
`orgId`	Yes	Organization ID
`realm`	Yes	Realm name
`userId`	Yes	User ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 14, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states what the operation does, but does not mention side effects, idempotency, whether it fails for non-members, or any impact on user roles/permissions.

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?

The description is a single, clear sentence that is easy to parse and front-loaded with the essential action. It is appropriately sized for a simple tool, though it could be slightly more informative without becoming verbose.

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 a simple removal operation with three required parameters and no output schema. The description is minimal and does not explain return behavior or edge cases, but for this level of complexity, a basic statement may suffice. Still, it leaves gaps about effects and error conditions.

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?

The schema provides descriptions for all three parameters (realm, orgId, userId), giving 100% coverage. The description adds no further semantic detail beyond the schema, so the baseline score of 3 is appropriate.

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 clearly states the action: 'Remove a user from an organization' with a specific verb and resource. It distinguishes from siblings like 'add-organization-member' and 'list-organization-members' by explicitly denoting the removal 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?

There is no guidance on when to use this tool vs alternatives, no prerequisites, no exclusion criteria. The description is purely a statement of action, leaving the agent to infer usage solely from the name and schema.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server