Skip to main content
Glama

Verify Player Email

horizon_verify_email
Idempotent

Verifies a player's email using the single-use token from their registration email, consumes it, and marks the email verified so the player can proceed to sign in.

Instructions

Verifies a player's email using the single-use token from their registration email. Use when: the player follows the verification email and explicitly requests completion. Not for: password reset tokens (use horizon_reset_password) or creating accounts (use horizon_signup_email). Side effects: consumes the verification token and marks the email verified. It does not sign in. Returns: empty HTTP 200 represented as null; then use horizon_signin_email. Errors: 400 for an invalid or expired verification token; request a fresh verification email through the approved account support flow. 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>"
    },
    "name": "horizon_verify_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesSingle-use token from the player's verification or password-reset email (max 256 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.11.1

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that the token is consumed, that the email becomes verified, that no session is created, and what the return value is (null / empty 200). It also documents failure behavior per status code (400 invalid/expired, 401 bad HORIZON_API_KEY cross-referenced to horizon_test_connection, 429 per-minute rate limit) and the required HORIZON_API_KEY. One minor tension: 'single-use token... consumes the token' sits awkwardly with idempotentHint=true, since a replay would error rather than repeat the effect, but the state outcome is unchanged and this does not contradict the readOnly/destructive claims.

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

Conciseness5/5

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

Front-loaded with the action, then cleanly labelled blocks (Use when / Not for / Side effects / Returns / Errors) that let an agent skim to the needed section. Every sentence adds information — no restatement of the tool name or filler.

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?

For a one-parameter tool with no output schema, the definition covers the trigger, the exclusion paths, the state change, the return value, the next step, auth requirements, and per-status error recovery. Nothing an agent needs to call it correctly, or to recover from a failure, is missing.

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

Parameters4/5

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

Schema coverage is 100% (type, min/max length, description), so the baseline is 3; the description earns extra by explaining what the token is, that it is single-use, and that it is consumed on success — semantics the schema does not carry. Minor residual ambiguity: the schema text says the token may come from a 'password-reset email' while the description forbids that path, so the agent must prefer the description.

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+resource pair ('verifies a player's email') and scopes it to the single-use token from the registration email. The 'Not for' line explicitly distinguishes it from horizon_reset_password and horizon_signup_email, so an agent can disambiguate without opening schemas.

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?

Gives an explicit trigger ('the player follows the verification email and explicitly requests completion'), explicit exclusions (password reset tokens, account creation), and names the correct sibling for each excluded case. It also states the follow-up tool (horizon_signin_email), which removes guesswork about the next step.

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