Skip to main content
Glama

Change Player Name

horizon_change_name
DestructiveIdempotent

Changes the authenticated player's display name to a confirmed new name using user ID and session token, returning auth status to confirm the change.

Instructions

Changes the authenticated player's display name using the matching user ID and current session. Use when: the player explicitly confirms a new display name. Not for: changing another player or account metadata. Use horizon_check_auth when session validity is uncertain. Side effects: replaces the player's current display name, with the same session validation and idle-time renewal as check-auth. Returns: AuthStatusResponse with isAuthenticated, authStatus and message. Check the response status/message to confirm the change. Errors: 400 for a blank or over-50-character name. Invalid sessions return 200 with isAuthenticated=false and INVALID_CREDENTIALS; they do not update the name. 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": {
      "userId": "<userId>",
      "sessionToken": "<sessionToken>",
      "newName": "<newName>"
    },
    "name": "horizon_change_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYesPlayer user ID (UUID) from the result of horizon_signup_* or horizon_signin_*
newNameYesNew display name confirmed by the player, from 1 to 50 characters
sessionTokenYesPlayer accessToken from signup, signin or refresh-session, passed as sessionToken (max 256 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.11.1

TDQS

A4.6/5.0
Behavior5/5

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

Goes well past the annotations, which only declare it as a destructive, idempotent, open-world write. The description supplies the actual side effect (the prior display name is replaced), the auth prerequisite (HORIZON_API_KEY), session/idle-time behavior, and a detailed failure taxonomy including the surprising 200-with-isAuthenticated=false case for invalid sessions, 400 for blank or >50-char names, 401 vs. 429 disambiguation, and that failures arrive as isError results.

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-loads the action in the first sentence and organizes the rest under Use when / Not for / Side effects / Returns / Errors labels, which makes it scannable. It is on the long side and the error paragraph is dense, but nearly every clause carries operational value for a mutation tool.

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 destructive, auth-gated mutation with no output schema, the definition covers the mutation's effect, required credentials, the exact response shape and how to confirm success, and the full error surface. An agent has everything needed to call it and interpret both success and failure.

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 all three parameters (UUID userId, 1–50 char newName, sessionToken source) are already documented. The description usefully restates validation (blank or over-50 names yield 400) and where the session comes from, but adds little semantic meaning 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 ('Changes the authenticated player's display name') and pins the scope to the authenticated player using userId plus sessionToken. It also explicitly separates itself from horizon_check_auth and from changing 'another player or account metadata', so an agent can distinguish it from siblings without opening a 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?

Gives an explicit trigger ('Use when: the player explicitly confirms a new display name'), explicit exclusions ('Not for: changing another player or account metadata'), and a named alternative for the ambiguous case ('Use horizon_check_auth when session validity is uncertain'). Little 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