Skip to main content
Glama

user_updatePassword

Update the password for an existing Operaton user. Provide the current password for non-admin accounts and receive confirmation on success.

Instructions

Update the password for an existing Operaton user. Requires the current password for non-admin users. Returns confirmation on success.

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": {
      "id": "<id>"
    },
    "name": "user_updatePassword"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.3.0
    • addedInput schema / additionalProperties
      Added value: +{}
    • addedInput schema / properties / id
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "id"
      +]
  2. First observedv1.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose two real behavioral traits: a conditional current-password requirement for non-admins and a confirmation return. It omits important traits for a credential mutation, such as required permissions/roles, password policy constraints, whether existing sessions are invalidated, and error behavior.

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?

Three short sentences, front-loaded with the action and followed by the prerequisite and return behavior. 'Returns confirmation on success' is close to filler but does set expectations, so the text remains efficient overall.

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?

This is a credential-mutating tool with no annotations, no output schema, and a schema that omits the password fields entirely, so the description must do the heavy lifting. It covers the prerequisite and the return but leaves permission requirements, policy rules, and session effects unstated, which is not enough for a security-sensitive write.

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

Parameters2/5

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

Schema coverage is 0% and only 'id' is defined, so the schema explains nothing. The description references a current password for non-admins, implying parameters that do not appear in the schema at all, and never explains 'id' (user id vs username). This leaves the caller with a confusing mismatch rather than added clarity.

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 uses a specific verb and resource ("Update the password for an existing Operaton user") and is clearly distinct from siblings such as user_updateProfile or user_unlock. It stops short of explicitly naming or contrasting those alternatives, which keeps it at 4 rather than 5.

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?

Usage is implied by the object (an existing user's password) and one prerequisite is stated ('Requires the current password for non-admin users'). There is no explicit guidance on when to choose this over user_updateProfile, or what an admin reset flow looks like.

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