Skip to main content
Glama

Sign In Anonymously

horizon_signin_anonymous

Sign in a returning guest and start a player session using the stored anonymous token. Use it before any tool that needs a session token.

Instructions

Signs in an anonymous (guest) account with its stored anonymousToken and starts a player session (accessToken). Use when: a returning guest opens the game, or right after horizon_signup_anonymous, before any tool that needs sessionToken. Not for: email accounts (use horizon_signin_email) or creating a guest (use horizon_signup_anonymous). Requires: the anonymousToken returned by horizon_signup_anonymous for this account. Side effects: creates a new session on every call; older sessions stay valid. Returns: {userId, username, accessToken, authStatus, message}. Pass userId and accessToken (as sessionToken) to the session tools; the token stays valid for one hour after its last use. Errors: 404 for an unknown anonymousToken: the account is lost, create a new one with horizon_signup_anonymous. 429 also comes from the per-token limit (5 attempts per minute) and the per-IP limit (30 per minute): wait a minute. 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
anonymousTokenYesanonymousToken returned by horizon_signup_anonymous (exactly 32 characters: letters, digits, _ and -)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.6.0
    • changedInput schema / properties / anonymousToken / description
      Previous value: -"anonymousToken returned by horizon_signup_anonymous (max 32 characters)"New value: +"anonymousToken returned by horizon_signup_anonymous (exactly 32 characters: letters, digits, _ and -)"
    • addedInput schema / properties / anonymousToken / minLength
      Added value: +32
    • addedInput schema / properties / anonymousToken / pattern
      Added value: +"^[A-Za-z0-9_-]+$"
  2. Changed1 schema field changedv1.5.5
    • changedInput schema / properties / anonymousToken / description
      Previous value: -"Anonymous token (max 32 characters)"New value: +"anonymousToken returned by horizon_signup_anonymous (max 32 characters)"
  3. First observedv1.5.4

TDQS

A4.6/5.0
Behavior5/5

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

The annotations already mark this as a non-read-only, non-idempotent, non-destructive, open-world operation. The description goes well beyond them by disclosing session side effects, token lifetime, rate limits, required API key, and error semantics, all consistent with 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 description is well structured with front-loaded sections for use, exclusions, requirements, side effects, returns, and errors. It is somewhat verbose, however, and the 429 explanation is repeated in the final sentence, slightly diluting conciseness.

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 authentication tool with no output schema, the description covers prerequisites, returns, session lifetime, side effects, and common failure modes. An agent has enough information to invoke it correctly and handle expected errors.

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 input schema already fully documents anonymousToken, including its exact format and origin. The description adds only a light reminder that the token comes from horizon_signup_anonymous for this account, without extra syntax or usage 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 description states a specific verb and resource: signs in an anonymous guest account and starts a player session. It distinguishes itself from siblings by naming horizon_signin_email and horizon_signup_anonymous as adjacent but different operations.

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?

It explicitly says when to use it ('returning guest opens the game', 'right after horizon_signup_anonymous') and when not to use it, naming both alternative tools. The routing guidance is complete enough that an agent can choose correctly without opening other schemas.

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