Skip to main content
Glama

Cancel Match Lobby

horizon_cancel_match
DestructiveIdempotent

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

Instructions

Executes cancel match lobby 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_cancel_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.6/5.0
Behavior3/5

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

Beyond the annotations it discloses meaningful behavior: lobby cancel is creator-only, departing actors receive metadata only and lose point-read access, failures return isError with HTTP status, and it enumerates 404/409/422/401/403/429 semantics. However, sentences such as "Start requires the creator and every joined UUID exactly once", "Turn requires the current unexpired actor" and "Timeout advances only one turn" belong to other operations and can mislead an agent about what this call does, which offsets the genuinely useful disclosure.

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

Conciseness2/5

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

The purpose leads, but the body is a sprawling block that mixes auth, side effects, returns, and a long error enumeration with boilerplate for start, turn, and timeout that does not apply here. Significant pruning would improve it; the density of unrelated clauses actively costs comprehension.

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 auth requirements (HORIZON_API_KEY, session), side effects, a return shape, and a full error taxonomy, which is close to what an agent needs. The residual issue is contamination by non-applicable match-lifecycle rules rather than missing information.

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, and the description earns above that by explaining that sessionToken must come from horizon_signin_email/anonymous, that a 403 means passing the userId that signed in, and that expectedRevision must never be replaced with a newer revision after an uncertain write. These are operational constraints the schema's field descriptions do not convey.

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

Purpose4/5

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

"Executes cancel match lobby under the exact original revision" names a specific verb and resource plus the revision precondition, which separates it from horizon_leave_match and the various horizon_cancel_* siblings. The core purpose is stated first and is unambiguous, though the phrasing "Executes cancel match lobby" is awkward and the surrounding sentences describe start/turn/timeout operations that this tool does not perform, diluting focus.

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?

It provides explicit "Use when" and "Not for" blocks and names siblings to reconcile: horizon_get_matches and horizon_get_match, with "timeout progression" implicitly routing to horizon_advance_match_timeout. The guidance is conditional and actionable, but the "Use when" clause ("explicit asynchronous multiplayer actions") is broader than this specific cancel operation, so the trigger is not perfectly sharpened to lobby cancellation.

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