Skip to main content
Glama

skycloak_create_realm_user

Create a Keycloak realm user in a specified cluster with an initial temporary password, optional names, and enabled status.

Instructions

Create a realm user with an initial temporary password.

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>",
      "username": "<username>",
      "email": "<email>",
      "temporary_password": "<temporary_password>"
    },
    "name": "skycloak_create_realm_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesthe email address
realmYesthe Keycloak realm name
enabledNowhether the user can sign in (defaults to true when omitted)
usernameYesthe username
last_nameNooptional last name
cluster_idYesthe cluster ID
first_nameNooptional first name
temporary_passwordYesinitial password (min 8 characters)

Output Schema

NameRequiredDescriptionDefault
idYes
emailYes
enabledYes
usernameYes
last_nameNo
first_nameNo
email_verifiedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world mutation. The phrase 'initial temporary password' adds genuine behavioral context — the user will likely be forced to change it at first login — but the description omits error behavior on duplicate username/email and any permission requirements.

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?

A single front-loaded sentence with zero filler; the key distinguishing detail (temporary password) is placed immediately after the core action.

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?

With 8 parameters, 5 required, existing annotations, and an output schema, the definition is minimally adequate — return values need not be explained. However, for a create-mutation requiring cluster_id and realm, the absence of duplicate-handling and prerequisite context leaves real gaps.

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 coverage is 100%, so all eight parameters including temporary_password (min 8 characters) and enabled (defaults to true) are already documented. The description adds only the nuance that the password is temporary, which the schema does not state explicitly; baseline 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 states a specific verb and resource ('Create a realm user'), which clearly separates it from siblings like get_realm_user, update_realm_user, and delete_realm_user. It does not explicitly name an alternative, but the operation is unambiguous.

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 versus alternatives, nor any prerequisites such as the realm needing to exist or what happens if the username or email already exists. The agent must infer all invocation context.

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