keycloak-mcp-server

create-role

Create a role in Keycloak at realm or client level. Provide realm name, role name, and optionally client ID to define client-specific roles.

Instructions

Create roles at realm or client level

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>",
      "roleName": "<roleName>"
    },
    "name": "create-role"
  }
}

Input Schema

Name	Required	Description
`realm`	Yes	Realm name
`clientId`	No	Client ID for client roles
`roleName`	Yes	Role name
`description`	No	Role description

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 14, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations, so description carries the full burden. It mentions realm/client level scope but does not disclose permissions, duplicate behavior, idempotency, or return results. For a mutation tool, this is insufficient.

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, no fluff, directly states purpose. Perfectly concise and front-loaded.

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?

Adequate for a simple create tool with well-documented schema, but lacks return value details and side-effect information (e.g., duplicate roles, permissions). Given no output schema and no annotations, more would be expected for full completeness.

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 has 100% description coverage, with all parameters meaningfully described (realm, clientId, roleName, description). The description adds no new semantic value beyond restating 'realm or client level', which is already in the schema.

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?

Clearly states it creates roles, with explicit scope at realm or client level. The verb 'Create' and resource 'roles' are specific, and the realm/client distinction distinguishes it from role management tools like update-role or delete-role.

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

Usage Guidelines3/5

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

Implied usage for creating simple roles, but no explicit guidance on when to choose this over create-composite-role or how to scope realm vs client. Sibling tools include create-composite-role, yet no differentiation is provided.

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

Deploy Server