Skip to main content
Glama

Reset Player Password

horizon_reset_password
DestructiveIdempotent

Sets a player's new password using a single-use email reset token and revokes all existing sessions. Use when the player confirms their new password after requesting a reset.

Instructions

Sets a new player password with the single-use reset token received by email and revokes existing sessions. Use when: the player explicitly confirms their new password after requesting horizon_forgot_password. Not for: verification tokens (use horizon_verify_email), account discovery or automatic password changes. Side effects: consumes the reset token, replaces the password and revokes all player sessions including refresh families. Clear corresponding local credentials and use horizon_signin_email again. Returns: empty HTTP 200 represented as null; no session or password is returned. Errors: 400 for an invalid/expired reset token, an out-of-range password or a rejected common password. Obtain a fresh reset email only at the player's request. 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": {
      "token": "<token>",
      "newPassword": "<newPassword>"
    },
    "name": "horizon_reset_password"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesSingle-use token from the player's verification or password-reset email (max 256 characters)
newPasswordYesNew password explicitly chosen by the player, 8 to 128 characters; common passwords are rejected; never returned

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.11.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description goes well past them: it discloses that the reset token is consumed, all sessions including refresh families are revoked, and the caller should clear local credentials and re-authenticate via horizon_signin_email. The Errors section maps 400/401/429 to concrete causes and notes every failure returns isError with status and body, which is actionable retry guidance an agent cannot get from the annotations.

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?

The prose is front-loaded with purpose, then cleanly sectioned into Use when / Not for / Side effects / Returns / Errors, so an agent can skim to the needed part. It is dense rather than padded, though the closing sentence bundling the 401-vs-horizon_test_connection diagnosis is slightly overloaded.

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?

There is no output schema, and the description compensates by stating the return is an empty HTTP 200 represented as null with no session or password returned. Combined with auth requirements (HORIZON_API_KEY), error taxonomy, and required caller follow-up, nothing an agent needs to invoke this destructive tool correctly 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 description coverage is 100%, so both parameters are already documented with length bounds and the common-password rejection rule, establishing a baseline of 3. The description restates the token's email origin and single-use nature and frames password errors (out-of-range, rejected common password), but adds no format or syntax detail beyond the schema.

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 opening sentence names the specific verb and resource ('Sets a new player password') plus the credential used ('single-use reset token received by email') and the side effect scope ('revokes existing sessions'). Siblings horizon_forgot_password and horizon_verify_email are named in adjacent roles, so an agent can distinguish this tool from them without opening any 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?

Explicit 'Use when' names the precondition (player confirms their new password after requesting horizon_forgot_password), and 'Not for' enumerates excluded cases including verification tokens routed to horizon_verify_email and automatic password changes. The alternative and the condition that selects it are both stated.

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