Skip to main content
Glama

Sign Up with Email

horizon_signup_email

Create a new player account with email, password, and display name to register new players and send email verification; account starts unverified. Sign in after verification.

Instructions

Creates a new player account with email, password and display name; the account starts unverified and without a session. Use when: a new player registers with email so the account can be recovered on other devices. Not for: existing accounts (use horizon_signin_email) and guest play without email (use horizon_signup_anonymous). Side effects: creates one player account and sends the verification email. It does not sign in. Returns: the new user with userId and isVerified: false. After the player verified the email address, call horizon_signin_email to get the accessToken. Errors: 409 when the email already belongs to an account: sign in with horizon_signin_email instead. 400 for an invalid email, a password outside 8 to 128 characters or a common password, or a bad name: fix the value and retry. 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).

Input Schema

NameRequiredDescriptionDefault
emailYesPlayer email address (valid format, max 40 characters); must not be registered yet
passwordYesPassword, 8 to 128 characters; common passwords such as "password1" are rejected. Sent to the API only, never returned
displayNameYesDisplay name shown on leaderboards (max 30 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.6.0
    • changedInput schema / properties / displayName / description
      Previous value: -"Display name (max 30 characters)"New value: +"Display name shown on leaderboards (max 30 characters)"
    • changedInput schema / properties / email / description
      Previous value: -"Email address (max 40 characters)"New value: +"Player email address (valid format, max 40 characters); must not be registered yet"
    • changedInput schema / properties / password / description
      Previous value: -"Password (4-32 characters)"New value: +"Password, 8 to 128 characters; common passwords such as \"password1\" are rejected. Sent to the API only, never returned"
    • changedInput schema / properties / password / maxLength
      Previous value: -32New value: +128
    • changedInput schema / properties / password / minLength
      Previous value: -4New value: +8
  2. First observedv1.5.4

TDQS

A4.6/5.0
Behavior5/5

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

Adds rich context beyond annotations: account starts unverified/no session, sends a verification email, does not sign in, and it documents error semantics (409, 400, 401, 429) plus required HORIZON_API_KEY. This is far beyond the minimal readOnly/destructive/idempotent hints.

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, then structured 'Use when/Not for/Side effects/Returns/Errors' blocks. Well organized, though the error block is dense and could be trimmed slightly.

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?

Given no output schema and a mutation tool, the description fully covers return value (userId, isVerified:false), side effects, follow-up workflow, and error handling. Nothing an agent needs to invoke 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 the schema already documents email/password/displayName constraints. The description restates some password length limits but adds little new semantic detail beyond the schema's baseline.

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?

Specific verb+resource ('Creates a new player account') with scope details ('starts unverified and without a session'). Explicitly distinguishes from siblings horizon_signin_email and horizon_signup_anonymous.

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' for new email registrations and 'Not for' naming the two alternatives (signin, anonymous signup). Also gives a follow-up flow when email is already taken.

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