Skip to main content
Glama

Sign Out Player

horizon_signout
DestructiveIdempotent

Revokes the current player session, or all of that player's sessions when explicitly requested, for logout and session revocation.

Instructions

Revokes the current player session on the server, or all of that player's sessions when explicitly requested. Use when: the player explicitly chooses logout, or chooses to revoke all sessions on their devices. Not for: only clearing an SDK cache or logging out a developer dashboard account. Use horizon_signin_* for a future login. Side effects: revokes current access and refresh family, or all user sessions if allSessions=true. Clear corresponding local credentials after confirmed success; SDK SignOut alone only clears local state. It does not revoke the anonymous recovery credential. Returns: empty HTTP 204 represented as null. allSessions omitted/false affects only the current session. Errors: 401 when the supplied access token is missing/invalid/expired. An error does not prove remote revocation; require signin if access has expired. 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": {
      "sessionToken": "<sessionToken>"
    },
    "name": "horizon_signout"
  }
}

Input Schema

NameRequiredDescriptionDefault
allSessionsNoRevoke all sessions for this user only when explicitly requested; omitted/false revokes the current session only
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 beyond the destructive/idempotent annotations: names exactly what is destroyed (access token and refresh family, or all user sessions), warns that local credentials must be cleared after confirmed success and that SDK SignOut alone only clears local state, notes the anonymous recovery credential survives, and spells out 401/429 error semantics 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?

Content is front-loaded with purpose followed by clearly labeled Use when / Not for / Side effects / Returns / Errors blocks, so an agent can scan it. It is dense and slightly overlong, but each labeled section carries distinct operational information rather than filler.

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 description supplies return shape (204 as null), the error taxonomy with remediation, rate-limit behavior, credential-lifecycle requirements, and the safety constraint on the allSessions flag. Nothing an agent needs to call it 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 coverage is 100%, so both parameters are already documented in the schema, including the same 'omitted/false revokes current session only' wording. The description's sentence about allSessions largely restates the schema, and the sessionToken lineage (accessToken from signup/signin/refresh) is also already in the schema. Baseline 3 with little added value.

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 (revokes) and resource (player session) and immediately distinguishes the two scopes: current session vs. all sessions when explicitly requested. An agent can tell this apart from sign-in/test-connection siblings 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' (player chooses logout or revoke-all), explicit 'Not for' (SDK cache clearing only, developer dashboard account logout), and a forward pointer to horizon_signin_* for future login. The when/when-not/alternative triad is fully covered.

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