Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

Reset User Password Direct

reset_user_password_direct
Destructive

Reset a user's password with a specific password value.

Instructions

Reset a user's password with a specific password value.

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

Input Schema

NameRequiredDescriptionDefault
user_idYesThe unique identifier of the user
passwordNoThe new password to set for the user (if None and generate_password is True, a random password will be generated)
password_lengthNoLength of the generated password if generate_password is True (default: 12)
generate_passwordNoWhether to generate a random secure password (default: False)
require_change_on_next_sign_inNoWhether to require the user to change password on next sign-in (default: True)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is known. The description adds nothing about consequences of a reset, session revocation, whether an existing password is overwritten, or how generate_password interacts with password. Beyond annotations, it offers no behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of filler. However, it is too sparse for a tool with two distinct operating modes and a password-change requirement, so the brevity reflects under-specification rather than crisp structure.

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 destructive mutation with five parameters, an output schema, and multiple modes, yet the description omits the generate-password path, the password_length behavior, and the require_change_on_next_sign_in default. For a security-sensitive reset operation, an agent needs more than one sentence to call it correctly.

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?

Schema description coverage is 100%, so the schema already documents all five parameters, including the generate_password fallback and require_change_on_next_sign_in default. The description only mirrors the idea of supplying a specific password and adds no syntax, exclusivity rules, or interaction details beyond the schema.

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 states a specific verb and resource: reset a user's password with a specific value. This clearly separates it from read-only password-method siblings, though the word 'direct' in the name is not explained and the generate-password mode in the schema is not acknowledged.

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?

There is no guidance on when to use this versus listing password methods or any other approach, and no prerequisites such as required permissions or whether the caller must have admin rights. The sentence gives no conditions for choosing this tool over alternatives.

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