iSuite Operations MCP Server

reset_user_password

Resets an iSuite user password by sending a reset email or returning a temporary password.

Instructions

Trigger a password reset for an iSuite user (sends reset email or returns temp password).

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

Input Schema

Name	Required	Description	Default
`userId`	Yes	The user's unique ID or username.
`sendEmail`	No	Send reset link via email (default true). If false, returns a temporary password.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 13, 2026

TDQS

A3.7/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. It explains the two behaviors based on sendEmail but does not disclose side effects like immediate invalidation of current password, security considerations, or prerequisites (e.g., user must exist). Adequate but incomplete.

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?

Single sentence conveying the essential action and two outcomes—no wasted words. Perfectly concise.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema is provided, and the description does not specify the return format or error conditions. The description covers the basic behavior but is incomplete for a mutation tool that may have side effects.

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 coverage is 100% with detailed parameter descriptions. The tool description adds no new information beyond what the schema already provides (e.g., sendEmail behavior is already in schema). Baseline 3 applies.

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 the tool triggers a password reset for an iSuite user, specifying two outcomes (sends email or returns temp password). It distinguishes from siblings like update_user or create_user by focusing on password reset.

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 implies the tool is for password resets but does not explicitly state when to use it versus alternatives (e.g., update_user for direct password change). No exclusions or context provided.

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