PurelyMail MCP Server

modify_user

Update a PurelyMail user account's username, password, password-reset permission, search-indexing setting, and two-factor authentication requirement.

Instructions

Modifies a user. Modifies a user.

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": {
      "userName": "<userName>"
    },
    "name": "modify_user"
  }
}

Input Schema

Name	Required	Description
`userName`	Yes	Full username, e.g. "user@domain.com"
`newPassword`	No	New password for user
`newUserName`	No	Full new username, e.g. "user@domain.com"
`enablePasswordReset`	No	Whether this user can have their password reset.
`enableSearchIndexing`	No	Whether search indexing should be enabled for this user. Indexes may take some time after enabling to be created.
`requireTwoFactorAuthentication`	No	Whether this user requires 2FA for login.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.0.2Nov 4, 2026

TDQS

D1.7/5.0

Behavior1/5

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

With no annotations, the description carries the full behavioral burden and discloses nothing. It does not state that this is a destructive mutation, whether changes are reversible, what permissions are required, or that password/2FA changes affect the user's login immediately.

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

Conciseness2/5

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

The text is two identical sentences, a pure duplication with zero informational content. Brevity here comes from under-specification rather than efficient editing, and there is no structure to front-load.

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

Completeness1/5

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

A 6-parameter mutation tool with no annotations and no output schema needs substantial disclosure about side effects and permissions. The description supplies none, leaving an agent unable to judge the impact of calling it.

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 every parameter including userName, newPassword, newUserName, and the three boolean flags is already documented in the schema. The description adds no meaning beyond it, which matches the baseline 3 for fully covered schemas.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Modifies a user" only restates the tool name and title; it names no verb-specific scope beyond generic mutation. It gives no hint of which aspects of a user can be changed (password, username, 2FA, indexing) and does not distinguish itself from create_user, delete_user, or update_domain_settings.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as delete_user or create_user. An agent must infer entirely from the name when this tool applies.

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