dendrite-admin-mcp

Reset a user's password

reset_password

Reset a user's password and optionally revoke all active sessions to regain account security.

Instructions

Set a new password for a local user, optionally invalidating all of their existing access tokens.

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": {
      "userId": "<userId>",
      "password": "<password>"
    },
    "name": "reset_password"
  }
}

Input Schema

Name	Required	Description
`userId`	Yes	Fully-qualified user ID, e.g. @alice:example.com
`password`	Yes	New password
`logoutDevices`	No	Invalidate all existing access tokens for this user

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 7, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the mutation (setting a new password) and the optional side effect of invalidating tokens, but it omits required permissions, irreversibility, session impact, or response behavior. The coverage is partial but not comprehensive.

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, front-loaded sentence with no unnecessary words. It directly states the action and the optional parameter effect.

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?

For a mutation tool with no annotations and no output schema, the description is too sparse. It doesn't mention whether admin authorization is required, what happens to active sessions (beyond optional token invalidation), or what the API response will be. This is a significant gap for a destructive operation.

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

Parameters4/5

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

Schema description coverage is 100%, so baseline is 3. The description adds the 'local user' constraint, which is not explicit in the schema's userId description, clarifying that remote users are not supported. This adds meaningful value beyond the schema.

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 uses the specific verb 'Set' with the resource 'new password for a local user', and also mentions the optional side effect of invalidating access tokens. This distinguishes it from sibling tools like register_user or refresh_devices.

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?

The description states the scope ('for a local user') but does not explicitly provide when-to-use compared to alternatives or mention prerequisites like admin permissions. While the context is clear, there is no explicit guidance or exclusions beyond the local-user constraint.

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

Deploy Server