keycloak-mcp-server

reset-user-password

Reset a user's password in a specific Keycloak realm. Provide realm, user ID, and new password to enforce security policies.

Instructions

Reset a user's password in a specific realm

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>",
      "userId": "<userId>",
      "newPassword": "<newPassword>"
    },
    "name": "reset-user-password"
  }
}

Input Schema

Name	Required	Description
`realm`	Yes	Realm name
`userId`	Yes	User ID
`temporary`	No	Whether password is temporary
`newPassword`	Yes	New password

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 must carry behavioral disclosure. It only states the action of resetting a password without mentioning side effects (e.g., invalidating sessions), required permissions, or implications of the 'temporary' flag. This is a significant gap for a sensitive mutation tool.

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?

The description is a single, eight-word sentence that is front-loaded with the verb and resource. It contains no filler or redundant words and is appropriately sized for a simple tool. Every word contributes to stating the core action.

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

Completeness2/5

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

The tool has no annotations, no output schema, and a minimal description. It lacks information about expected response, side effects, or when to use the 'temporary' parameter. For a password reset operation with four parameters, the description is insufficient for confident invocation.

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 already documents all four parameters with descriptions, achieving 100% coverage. The description adds no extra semantic value beyond restating the realm scoping. It does not clarify interactions like whether 'temporary' forces a password change on next login, so it stays at the baseline.

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 the specific verb 'Reset' and clearly identifies the resource ('a user's password') and scope ('in a specific realm'). It distinguishes itself from sibling tools like update-user and logout-user by focusing on password reset. The action is unambiguous, especially with the newPassword parameter in the schema.

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?

The description provides no guidance on when to use this tool versus alternatives such as update-user or set-user-attributes. It does not mention any prerequisites, exclusions, or preferred contexts. The mention of 'specific realm' is a scoping detail rather than usage guidance.

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

Deploy Server