Skip to main content
Glama

Join Match

horizon_join_match
Idempotent

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

Instructions

Executes join 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_join_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

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=true, but the description goes well beyond them: one HTTP attempt, expectedRevision semantics, 404 masking private/expired matches, 409 REVISION_CONFLICT requiring explicit reread rather than resubmission, 422 ACCOUNT_MATCH_LIMIT_REACHED applying only to create, 501 for simpleServer ranked mode, 401/403 session disambiguation, HORIZON_API_KEY dependency and 429 rate limiting. It also discloses state consequences such as a forfeit on active leave and metadata-only access after departing a lobby.

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) that make a dense block scannable. The error catalog is long but each entry carries actionable routing information rather than filler. The one structural weakness is that the 'Side effects' sentence mixes in sibling-owned operations, which blurs the tool's scope inside an otherwise tight layout.

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?

There is no output schema, and the description compensates by stating the return shape ({match, pollAfterSeconds, serverTime}) and the metadata-only downgrade for departing lobby actors. Combined with auth requirements, error taxonomy and revision discipline, an agent has everything needed to call and recover from failures without opening other tools.

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 the schema already documents all four parameters and the baseline is 3. The description adds some real meaning on top — that userId must match the signed-in session and that 403 means the token belongs to another user, plus the 'never substitute a newer revision' constraint on expectedRevision. However it never explains how matchId relates to the selected project or what the revision values look like in practice, so the added value is moderate rather than substantial.

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?

Opens with a specific verb and resource: 'Executes join match under the exact original revision', which tells an agent this is the commit action for joining, not a read. It distinguishes itself from siblings by naming horizon_get_matches and horizon_get_match for reconciliation. The only clarity cost is the 'Side effects' sentence, which enumerates Start/Turn/Timeout/Leave/Cancel behaviors that belong to dedicated siblings (horizon_start_match, horizon_submit_match_turn, horizon_leave_match, horizon_cancel_match) and can make an agent wonder whether this tool also performs those actions.

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 an explicit 'Not for' list excluding polling, page traversal, timeout progression, invented winners and automatic rewards. Prerequisites are spelled out operationally: sign in via horizon_signin_email or horizon_signin_anonymous and pass its accessToken as sessionToken. It also routes the agent to reconcile via horizon_get_matches / horizon_get_match before retrying.

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