PurelyMail MCP Server

create_user

Creates a new PurelyMail user account from a username, domain, and password; optionally sets recovery details and welcome email preferences.

Instructions

Creates a user. Creates a new 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>",
      "domainName": "<domainName>",
      "password": "<password>"
    },
    "name": "create_user"
  }
}

Input Schema

Name	Required	Description
`password`	Yes
`userName`	Yes	Local part of username, e.g. "user" in "user@domain.com"
`domainName`	Yes
`recoveryEmail`	No
`recoveryPhone`	No
`sendWelcomeEmail`	No
`enablePasswordReset`	No
`enableSearchIndexing`	No
`recoveryEmailDescription`	No
`recoveryPhoneDescription`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.0.2Nov 4, 2026

TDQS

D1.3/5.0

Behavior1/5

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

No annotations are supplied, so the description carries the full behavioral burden and discloses nothing. It does not say whether the account is immediately active, whether a welcome email is sent by default, whether password reset is enabled, whether the operation is reversible, or what permissions are required — all of which matter for a write operation creating an identity.

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?

It is short, but the brevity is under-specification rather than efficiency, and the second sentence is a verbatim restatement of the first — pure waste with no informational value. There is no structure to front-load because there is essentially no content.

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?

For a 10-parameter mutation tool with no annotations and no output schema, this description is completely inadequate. An agent cannot determine required setup, side effects, or return behavior from it, and the schema's undocumented fields leave large blind spots.

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

Parameters1/5

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

Schema description coverage is only 10% across 10 parameters, so the description must compensate and instead adds zero meaning. Nothing explains domainName format, what recoveryEmail/recoveryPhone descriptions are for, or what the three boolean defaults (sendWelcomeEmail, enablePasswordReset, enableSearchIndexing) actually do when toggled.

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?

The description says only "Creates a user. Creates a new user." The first sentence gives a bare verb+resource, but the second merely repeats it with no added specificity. It gives no indication of what kind of user (directory/mailbox user in a domain), and nothing distinguishes it from siblings like modify_user, add_domain, or create_app_password.

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 at all: no mention of prerequisites such as an existing domain, no indication of when to prefer modify_user or create_or_update_password_reset_method, and no exclusions. An agent has to infer the entire usage context from the tool name.

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