Skip to main content
Glama

Advance Match Timeout

horizon_advance_match_timeout
DestructiveIdempotent

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

Instructions

Executes advance match timeout 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_advance_match_timeout"
  }
}

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

B3.2/5.0
Behavior3/5

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

Annotations already declare destructive=true, idempotent=true and openWorld=true; the description goes further with real behavioral detail a schema can't carry — one HTTP attempt, 404 masking of private/missing/expired matches, 409 REVISION_CONFLICT requiring explicit reread rather than resubmission, 422 ACCOUNT_MATCH_LIMIT_REACHED applying to create only, 429 rate limiting, and 401/403 session recovery. However, a substantial portion of the disclosure (Start requires creator and all joined UUIDs, Timeout advances one turn, lobby cancel is creator-only) documents other operations, so the behavioral picture for this specific tool is muddied rather than complete.

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?

It is front-loaded with labeled sections (Use when, Not for, Requires, Side effects, Returns, Errors), which helps scanning, but it is an extremely dense single block that packs multiple error taxonomies and unrelated action semantics together. Several sentences about start/turn/leave/cancel do not earn their place in a timeout-advance tool's description.

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 description covers auth source, the returned shape ({match, pollAfterSeconds, serverTime}), conflict handling and the full error taxonomy, which is close to what an agent needs to call it safely. It loses a point because the conflation of this tool's behavior with sibling actions leaves the actual scope of a successful call less clear than the error detail suggests.

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 four parameters are already documented and the baseline is 3. The description adds a little operational meaning — the sessionToken must come from a horizon_signin_* call and be sent as Bearer, and expectedRevision must never be replaced after an uncertain write — but that is mostly restating what the schema fields already say.

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?

"Executes advance match timeout under the exact original revision" largely restates the name plus the expectedRevision constraint, so the core operation is only minimally clarified. The scope is then blurred because the Side effects block describes start, turn, leave, cancel and report behaviors that belong to sibling tools (horizon_start_match, horizon_submit_match_turn, horizon_leave_match, horizon_cancel_match, horizon_report_match_result), leaving the agent unsure what this single call actually does.

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?

Explicit prerequisites (sign in with horizon_signin_email/horizon_signin_anonymous and pass accessToken as sessionToken), a Use-when line, a Not-for exclusion list, and a reconciliation instruction pointing at horizon_get_matches and horizon_get_match. The only gap is that the Use-when phrase ("explicit asynchronous multiplayer actions") is broad enough that it doesn't sharply separate this tool from the turn/start siblings it also describes.

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