Skip to main content
Glama

Request Player Password Reset

horizon_forgot_password

Requests a password-reset email for a player who explicitly asks for account recovery without revealing whether the email is registered.

Instructions

Requests a password-reset email for a player without disclosing whether the email is registered. Use when: the player explicitly requests password recovery for this email address. Not for: account discovery, repeated email sends or resetting the password itself (use horizon_reset_password). Side effects: may send a reset email and replace the previous reset token. Never automatically repeat an uncertain request. Returns: empty HTTP 200 represented as null regardless of whether the email exists; it does not prove delivery or account existence. Errors: 400 for an invalid email; common API errors are surfaced without attempting automatic retries. Needs HORIZON_API_KEY. Every failure returns an error result (isError) with the HTTP status and body: a 401 that horizon_test_connection also returns means HORIZON_API_KEY is wrong, 429 means the account's per-minute rate limit was reached (wait a minute, then retry).

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": {
      "email": "<email>"
    },
    "name": "horizon_forgot_password"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesPlayer's email address for the explicitly requested password recovery (max 254 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.11.1

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the annotations (which only mark it non-read-only, non-idempotent, open-world): it discloses side effects (sends an email, replaces the previous reset token), the enumeration-safe empty 200/null response, that success does not prove delivery, and a full error taxonomy (400 invalid email, 401 = bad HORIZON_API_KEY per horizon_test_connection, 429 per-minute rate limit with wait-and-retry). Requires HORIZON_API_KEY. Minor redundancy between "never automatically repeat an uncertain request" and "errors are surfaced without automatic retries" keeps it from a 5.

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?

Front-loaded purpose sentence followed by labeled sections (Use when / Not for / Side effects / Returns / Errors), which makes it easy to scan. It is longer than typical but nearly every line carries decision-relevant information; only the retry caution is slightly duplicated.

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

Completeness5/5

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

No output schema, yet the description covers the return value (empty HTTP 200 as null, not proof of delivery or existence), side effects, auth requirement, and error handling with status-specific remediation. Nothing an agent needs to call this safely is missing.

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% and the email parameter already carries format, pattern, maxLength, and a description, so the schema does the heavy lifting. The description adds only that an invalid email yields a 400, which is behavioral rather than new parameter semantics. Baseline 3 is appropriate.

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?

States a specific verb and resource ("Requests a password-reset email for a player") plus the key security property (no disclosure of whether the email is registered). It explicitly distinguishes itself from the sibling horizon_reset_password, so an agent can route without opening either schema.

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

Usage Guidelines5/5

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

Uses explicit when/when-not framing: use when the player explicitly requests recovery for this address; not for account discovery, repeated sends, or actually resetting the password (routes to horizon_reset_password). It also adds a caution against automatically repeating an uncertain request.

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

Deploy Server

Other Tools