Skip to main content
Glama

Leave Match

horizon_leave_match
DestructiveIdempotent

Executes leave match under the exact original revision. Use when: explicit asynchronous multiplayer actions after reading horizon://docs/matches.

Instructions

Executes leave match under the exact original revision. Use when: explicit asynchronous multiplayer actions after reading horizon://docs/matches. Not for: automatic polling, page traversal, timeout progression, invented winners or automatic rewards. Reconcile with horizon_get_matches and horizon_get_match. Consent and game consensus do not validate honest gameplay. Requires: userId and the player's session: sign in with horizon_signin_email or horizon_signin_anonymous and pass its accessToken as sessionToken. Side effects: One HTTP attempt. Start requires the creator and every joined UUID exactly once. Turn requires the current unexpired actor. Timeout advances only one turn. Active leave forfeits without selecting a winner. Lobby cancel is creator-only. Full Inbox retains a durable notice without undoing a committed move. Returns: {match,pollAfterSeconds,serverTime}; departing lobby actors receive metadata only and lose point-read access. Errors: 404 hides private/missing/expired matches. 409 REVISION_CONFLICT or STATE_CONFLICT: explicitly reread and reconcile the original intent, never replace the revision or automatically resubmit. RESULT_CONFLICT preserves the original report. RUN_EXPIRED/RUN_ALREADY_USED never allow replacement ranked runs. 422 ACCOUNT_MATCH_LIMIT_REACHED refuses create only, when the account's open matches (lobby, running, reporting) across all its projects are at the plan limit; join, turns, leave, report and cancel are not blocked, so wait for matches to finish instead of retrying. 501 FEATURE_NOT_SUPPORTED is explicit for simpleServer ranked mode. 401 means the session is missing or expired: sign in again and retry with the new accessToken. 403 for a session means the token belongs to another user: pass the userId that signed in. 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>",
      "matchId": "<matchId>",
      "expectedRevision": "<expectedRevision>"
    },
    "name": "horizon_leave_match"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYesActive player matching the session and project
matchIdYesOriginal server match UUID in the selected project
sessionTokenYesPlayer accessToken sent only as Bearer
expectedRevisionYesOriginal reviewed revision; never substitute a newer revision after an uncertain write

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.9.1

TDQS

A3.7/5.0
Behavior4/5

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

Well beyond the annotations, it discloses auth sourcing (accessToken from horizon_signin_email/horizon_signin_anonymous, HORIZON_API_KEY), single-HTTP-attempt semantics, rate limiting (429), account match limits (422 applies to create only), privacy behavior on 404, and that an active leave forfeits without selecting a winner. There is mild tension with idempotentHint=true, since it forbids automatic resubmission after 409, though that is conflict-specific guidance rather than a direct contradiction; the inclusion of start/turn/timeout side effects also dilutes focus.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and the labeled sections (Use when / Not for / Requires / Side effects / Returns / Errors) make it scannable. But it is a dense block in which several sentences describe operations this tool does not appear to perform (start, turn, timeout, lobby cancel), and the error catalogue is long enough to bury the leave-specific information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, open-world mutation with no output schema, the definition covers return shape ({match,pollAfterSeconds,serverTime}), authentication, and a full status-code taxonomy including conflict, expiry, limit, and rate-limit cases. The one shortfall is that the multi-action side-effect narrative leaves unresolved whether this tool performs anything beyond leaving, given the schema has no action discriminator.

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: sessionToken must be the accessToken from a specific sign-in tool, userId must be the account that signed in (reinforced by the 403 guidance), and expectedRevision must be the original reviewed revision with no substitution after an uncertain write. That is genuine semantics beyond the field descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence states a verb and resource ("Executes leave match under the exact original revision"), which matches the name and title. However, the body then describes behaviors for Start, Turn, Timeout, and Lobby cancel, none of which correspond to any action parameter in the four-parameter schema, so an agent cannot tell from the description what this specific tool actually does versus the rest of the match-action family.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The "Use when" / "Not for" structure is explicit: it names the prerequisite (read horizon://docs/matches first), excludes polling, page traversal, timeout progression, and invented winners, and points to horizon_get_matches and horizon_get_match for reconciliation. The gap is that "explicit asynchronous multiplayer actions" is generic across the whole family rather than specific to leaving, so the guidance is clear but not tailored to this tool.

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