PurelyMail MCP Server

create_or_update_password_reset_method

Creates or updates a user's email or phone password reset method, with optional MFA reset support and updates to existing targets to avoid duplicates.

Instructions

Creates or updates a password reset method (either phone or email).

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>",
      "type": "<type>",
      "target": "<target>"
    },
    "name": "create_or_update_password_reset_method"
  }
}

Input Schema

Name	Required	Description
`type`	Yes	Type of password reset, either 'email' or 'phone'
`target`	Yes	Email address or phone number
`userName`	Yes	Username
`description`	No	Human-readable description
`allowMfaReset`	No	Whether this method should allow a user's MFA to be reset as well (defaults to true)
`existingTarget`	No	Target from list operation. If provided, update existing method matching target instead of creating a new one.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.0.2Nov 4, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden but discloses almost nothing: it doesn't state whether an upsert replaces or adds a method, what permissions are required, side effects of the allowMfaReset default, or what happens if the target already exists without existingTarget.

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

Conciseness4/5

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

It is a single tight sentence with no filler and the core purpose is front-loaded. It is efficient, though the brevity contributes to the missing behavioral detail rather than being purely a virtue.

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 six-parameter mutation tool with no annotations and no output schema, the description is too thin. The create-vs-update distinction, the effect of allowMfaReset, and error behavior around existing targets all matter to an agent but are left unaddressed.

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 is already documented, including the meaningful existingTarget and allowMfaReset fields. The description adds only the 'phone or email' framing for type, which the schema already covers, so it meets but does not exceed the baseline.

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 names a specific verb+resource pair (create/update a password reset method) and clarifies the two possible channels (phone or email). This clearly separates it from siblings like delete_password_reset_method and list_password_reset_methods, though it doesn't explicitly mention them.

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 call this versus list_password_reset_methods or delete_password_reset_method, nor any explanation of when the tool creates versus updates. The critical decision logic (supply existingTarget to update) is only present in the schema, not the description.

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