Skip to main content
Glama

Sign Up with Apple

horizon_signup_apple

Creates a new Apple player account from a consented identity token after sign-in returns USER_NOT_FOUND, with optional first-login name and refresh session. It does not auto-link accounts.

Instructions

Creates an Apple player with a consented identity token and optional first-login name fields. Use when: horizon_signin_apple returned USER_NOT_FOUND and the player explicitly agrees to create the account. Not for: signup after any other Apple failure, dashboard-account login, or automatic account linking. Requires: Apple Sign-In enabled for this project API key with matching Team ID, Services ID and/or Bundle ID in the dashboard, and an identity token from the app's native or browser consent flow. Side effects: creates a player. The server derives the name from appleFirstName/appleLastName or the token; use horizon_change_name for an override. No session without refresh opt-in. Returns: 201 with userId, appleUserId, isPrivateRelayEmail, isVerified and authStatus. includeRefreshToken=true also issues accessToken, refreshToken and both expiry timestamps. Otherwise call horizon_signin_apple after signup. Errors: 400 INVALID_APPLE_TOKEN or APPLE_NOT_CONFIGURED requires fixing the token/configuration, 409 means identity/email conflict. Do not create or link another account automatically. 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": {
      "appleIdentityToken": "<appleIdentityToken>"
    },
    "name": "horizon_signup_apple"
  }
}

Input Schema

NameRequiredDescriptionDefault
appleLastNameNoOptional family name from Apple's first consent response (max 50 characters); Apple may not send it again
appleFirstNameNoOptional given name from Apple's first consent response (max 50 characters); Apple may not send it again
appleIdentityTokenYesApple identity-token JWT obtained after player consent, with audience matching this project's configured Services ID or Bundle ID
includeRefreshTokenNoExplicit opt-in to a rotating 30-day refresh session; omitted or false preserves access-only behavior. Store refresh tokens in platform secure storage

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.11.1

TDQS

A4.8/5.0
Behavior5/5

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

Goes well past the annotations: it discloses that a player is created, that the server derives the name from appleFirstName/appleLastName or the token (with horizon_change_name as the override path), and that no session is issued without refresh opt-in. It also documents return shape (201 with userId, appleUserId, isPrivateRelayEmail, isVerified, authStatus), error semantics for 400/409/401/429, and the HORIZON_API_KEY requirement.

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?

Labeled sections (Use when, Not for, Requires, Side effects, Returns, Errors) make it scannable and front-load the routing decision. The Errors paragraph is dense with two separate failure narratives (auth vs. rate limit) that could be tightened, but nothing is gratuitous.

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 non-idempotent, open-world account-creation mutation with no output schema, the description covers prerequisites, side effects, success payload, error codes and retry guidance. An agent has everything needed to call it correctly and to decide what to do on failure.

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%, so the baseline is 3, but the description adds real meaning: appleFirstName/appleLastName are secondary to the token-derived name and are only the override path via horizon_change_name, and includeRefreshToken actually issues accessToken, refreshToken and expiry timestamps. It does not add token-format or audience-matching detail beyond what the schema already states.

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 an Apple player with a consented identity token and optional first-login name fields.' It is immediately distinguishable from the sibling sign-in tool, which the description references by name, and from other signup variants (google/email/anonymous) by naming the Apple identity token input.

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 ('Use when: horizon_signin_apple returned USER_NOT_FOUND and the player explicitly agrees') and explicit exclusions ('Not for: signup after any other Apple failure, dashboard-account login, or automatic account linking'). It also routes the post-signup flow to horizon_signin_apple when no refresh token was requested.

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