Skip to main content
Glama

Submit Match Turn

horizon_submit_match_turn
DestructiveIdempotent

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

Instructions

Executes submit match turn 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>",
      "dataBase64": "<dataBase64>",
      "finish": "<finish>"
    },
    "name": "horizon_submit_match_turn"
  }
}

Input Schema

NameRequiredDescriptionDefault
finishYesTrue freezes final bytes and opens reporting without choosing a winner
userIdYesActive player matching the session and project
matchIdYesOriginal server match UUID in the selected project
dataBase64YesOriginal opaque bytes, including empty state. Never interpret or silently replace them
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

A4.5/5.0
Behavior5/5

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

Annotations already flag destructive/openWorld/idempotent, and the description still adds substantial context beyond them: one HTTP attempt per call, per-action side effects (start requires creator plus every joined UUID exactly once, timeout advances only one turn, active leave forfeits without picking a winner), and the warning that consent/consensus does not validate honest gameplay. It documents return shape, 404 masking of private/expired matches, 409 reconcile-do-not-resubmit, 422 account-limit scoping, 429 rate limit and HORIZON_API_KEY/401/403 auth recovery. No conflict with the declared hints.

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?

Well front-loaded with labeled sections (Use when / Not for / Requires / Side effects / Returns / Errors), so it scans quickly despite its length. Nearly every sentence carries operational information, though the error section is dense enough that some clauses (e.g. the long 422 plan-limit explanation) could be compressed. Length is defensible for a destructive, multi-state mutation.

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?

No output schema exists, yet the description supplies the return shape {match,pollAfterSeconds,serverTime}, the auth prerequisite chain, side-effect semantics per action type, and the full status-code contract including retry-vs-wait guidance. For a destructive tool with six required parameters and rich failure modes, 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.

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 meaning the schema does not: sessionToken must be the accessToken from horizon_signin_email/horizon_signin_anonymous, expectedRevision must never be replaced with a newer revision after an uncertain write, and userId must be the user who signed in (403 otherwise). The only gap is that finish and dataBase64 are largely left to their schema text.

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 submit match turn under the exact original revision" names the verb and resource, and the surrounding clauses (current unexpired actor, one turn per call) make the operation concrete. It separates itself from adjacent operations by excluding "timeout progression" and pointing at horizon_get_matches / horizon_get_match for reconciliation. The only weakness is the slightly self-referential phrasing of the opening sentence, which mirrors the tool name.

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: explicit asynchronous multiplayer actions after reading horizon://docs/matches" and "Not for: automatic polling, page traversal, timeout progression, invented winners or automatic rewards." It also names the reconciliation tools (horizon_get_matches, horizon_get_match) and the sign-in prerequisites that gate use, so an agent knows both when to call it and what to do first.

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