Skip to main content
Glama

Sign Up Anonymously

horizon_signup_anonymous

Create an anonymous player account with only a display name. Returns an anonymousToken to store for later sign-in, useful for guest play without email.

Instructions

Creates a new anonymous (guest) player account that needs only a display name and returns its anonymousToken. Use when: a player starts without email, for example on first launch of a game with guest play. Not for: players who sign up with email and password (use horizon_signup_email) or returning guests (use horizon_signin_anonymous with the stored anonymousToken). Side effects: creates one new player account per call; calling it again creates another account, it never finds an existing one. Sign-up starts no session. Returns: {userId, username, isAnonymous: true, anonymousToken, createdAt}. Store anonymousToken on the device: it is the only way back into this account. Then call horizon_signin_anonymous to get the accessToken that session tools need. Errors: 400 for an invalid displayName: fix the name 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
displayNameYesDisplay name shown on leaderboards (max 30 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.0
    • changedInput schema / properties / displayName / description
      Previous value: -"Display name for the anonymous user (max 30 characters)"New value: +"Display name shown on leaderboards (max 30 characters)"
  2. First observedv1.5.4

TDQS

A4.7/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: one account created per call with no lookup semantics, no session started, the anonymousToken being the only way back in, the need for HORIZON_API_KEY, and per-status error handling (400/401/429). The annotations already cover non-idempotence and open-world behavior, and the description reinforces and extends that with the retry and storage guidance.

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?

Dense but well partitioned into Use when / Not for / Side effects / Returns / Errors, with the core purpose front-loaded. Every labeled sentence carries unique operational value (idempotence caveat, token storage, error triage) rather than repeating structured fields.

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?

Even without an output schema, the description enumerates the return object fields and the follow-up call (horizon_signin_anonymous) needed for a session. For a low-complexity, 1-param signup tool this leaves no meaningful gap.

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%, so the single displayName parameter (with its 30-char limit) is fully documented by the schema. The description reinforces that only a display name is needed and adds the 400-invalid-name failure mode, but adds no syntax 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?

States a specific verb and resource ('Creates a new anonymous (guest) player account') plus the exact return artifact ('returns its anonymousToken'). It explicitly distinguishes itself from the email-signup and returning-guest siblings, so an agent can route correctly 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' and 'Not for' clauses name the alternatives (horizon_signup_email, horizon_signin_anonymous with stored token) and the selecting condition (no email / first guest launch). Nothing is left to inference.

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