Skip to main content
Glama
Sign In
mcp-keycloak

mcp-keycloak

by idoyudha
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

reset_user_password

Reset a user's password with support for temporary passwords that require change on next login.

Instructions

Reset a user's password.

Args:
    user_id: The user's ID
    password: New password
    temporary: Whether the password is temporary (user must change on next login)
    realm: Target realm (uses default if not specified)

Returns:
    Status message

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": {
      "user_id": "<user_id>",
      "password": "<password>"
    },
    "name": "reset_user_password"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYes
passwordYes
temporaryNo
realmNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description only says 'Reset a user's password' and 'Returns: Status message,' omitting side effects like session invalidation or notification.

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 concise with a clear one-line purpose, followed by structured Args and Returns sections, every sentence adding value.

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?

Missing behavioral context (e.g., permissions, side effects) and usage guidance; output schema exists but return is vague ('Status message'), insufficient for a security-sensitive tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All four parameters (user_id, password, temporary, realm) are explained with clear meanings and defaults, compensating for the input schema's lack of descriptions (0% coverage).

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 'Reset a user's password' with a specific verb and resource, distinguishing it from sibling tools like update_user or logout_user.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., update_user) or prerequisites like admin permissions.

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