Skip to main content
Glama

Set User Password

set_user_password
Destructive

Sets another user's password directly without an email reset, requiring confirmation because the previous password is permanently replaced.

Instructions

(Admin) Fija la clave de otro usuario sin pasar por el correo. Pide confirmación (la clave anterior se pierde).

Pisa cualquier clave que el usuario haya puesto con «olvidé mi contraseña». Si la nueva clave es un RUT, Orbits le pedirá cambiarla al iniciar sesión. La clave nunca se devuelve ni se registra.

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>",
      "new_password": "<new_password>"
    },
    "name": "set_user_password"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYes
new_passwordYes
confirm_tokenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Goes well past the destructiveHint/idempotentHint annotations by explaining the concrete consequence (the previous password is lost), that it overrides any password the user set via 'forgot my password', and that a RUT-shaped password forces a change at next login. It also states the password is never returned or logged, which is valuable output/security context.

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?

Four tight sentences, front-loaded with the admin scope and the destructive parenthetical warning immediately after the verb. No filler, though the password-policy sentence could be merged for slightly tighter flow.

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

Completeness4/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 safety/destructive profile is covered, so the remaining burden is behavioral, which the description handles well. The one omission is the unexplained confirm_token parameter, which matters for actually invoking the tool successfully.

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?

With 0% schema description coverage, the description must carry all parameter meaning. It conveys user_id (another user's account) and new_password behavior (RUT triggers forced change), but confirm_token is never explained even though the description alludes to a confirmation step without saying it maps to that parameter.

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?

States a specific verb and resource (set another user's password), with an explicit admin-only scope and the explicit absence of the email flow. It is clearly distinguishable from siblings like update_user or login, though it never names a sibling directly to reinforce that distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives strong context for when this is the right tool: admin acting on another user's account, no email round-trip, and a confirmation step required. It does not name an alternative for related account operations, so the routing guidance is contextual rather than explicit.

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