Skip to main content
Glama

skycloak_update_realm_user

Idempotent

Update a Keycloak realm user's profile fields—email, first and last name, enabled status, and email verification—by specifying the cluster, realm, and user ID.

Instructions

Update a realm user's profile (email, name, enabled, email_verified).

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>",
      "user_id": "<user_id>"
    },
    "name": "skycloak_update_realm_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNonew email address
realmYesthe Keycloak realm name
enabledNowhether the user can sign in
user_idYesthe user ID
last_nameNonew last name
cluster_idYesthe cluster ID
first_nameNonew first name
email_verifiedNowhether the email is verified

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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only the set of mutable fields, not the important behavior for an update tool: whether omitted fields are left unchanged (partial update), whether changes are reversible, or what permissions are required.

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?

A single front-loaded sentence with no filler, though the brevity comes at the cost of the partial-update semantics noted above.

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?

An output schema exists and the schema is fully described, so return values and parameter meanings needn't be repeated. However, for a mutation tool with three required identifiers and five optional fields, the description should state how partial updates behave; that gap is the main incompleteness.

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 description coverage is 100%, so every parameter is already documented in the schema, and the description merely echoes the field names. It does not clarify that only cluster_id, realm, and user_id are required while all profile fields are optional, which is the one piece of semantic clarity that would have added value.

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 gives a specific verb and resource ('Update a realm user's profile') and enumerates the editable attributes (email, name, enabled, email_verified), which cleanly separates it from siblings like delete_realm_user, get_realm_user, or assign_realm_user_role. It doesn't explicitly contrast with those siblings, but the resource 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 when-to-use guidance: it doesn't say the user must already exist, doesn't point to skycloak_create_realm_user for creation, and doesn't mention that group/role memberships are handled by other tools. Usage is only implied by the verb 'update'.

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