Skip to main content
Glama

Create Match

horizon_create_match
Idempotent

Creates one server-ID lobby under the original player-ledger revision. Use when: explicit asynchronous multiplayer actions after reading horizon://docs/matches.

Instructions

Creates one server-ID lobby under the original player-ledger 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. Reserves active and settlement capacity plus bounded invite slots atomically and counts against the account-wide open match cap. Completed detail history is separate; FREE defaults to zero. Lost response: reconcile horizon_get_matches with the original intent. Returns: {match,playerRevision,pollAfterSeconds,serverTime} 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>",
      "expectedRevision": "<expectedRevision>",
      "settings": "<settings>"
    },
    "name": "horizon_create_match"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYesActive player matching the session and project
settingsYesComplete immutable lobby settings; current tier state cap also applies
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.8/5.0
Behavior5/5

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

Goes far past the annotations: it discloses that only one HTTP attempt is made, that active and settlement capacity plus bounded invite slots are reserved atomically and count against the account-wide open match cap, that lost responses must be reconciled rather than retried, and that FREE defaults to zero. The error catalogue (REVISION_CONFLICT / STATE_CONFLICT / RESULT_CONFLICT / RUN_EXPIRED / 422 limit semantics) tells the agent exactly which failures forbid resubmission, which is behavior nothing in the annotations conveys.

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?

Long but front-loaded and labeled (Use when / Not for / Requires / Side effects / Returns / Errors), so an agent can scan the routing cues first. A few passages are wordy (the 401-vs-HORIZON_API_KEY tie-in and the repeated 'never retry' phrasing), but nearly every line carries operational information.

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?

For a 4-parameter, nested-settings mutation with openWorld and idempotent hints and no output schema, the description supplies returns shape, atomic side effects, auth prerequisites and per-error recovery guidance. There is no meaningful ambiguity left about how to call it or how to recover from a failure.

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 already 100%, so the baseline is 3, but the description adds real meaning: it explains that sessionToken is the accessToken from horizon_signin_email/anonymous, and that expectedRevision must be the originally reviewed revision and never substituted after an uncertain write. It also frames the settings object as complete immutable lobby state where dataBase64 must never be reinterpreted or replaced.

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

Purpose5/5

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

States a specific verb and resource: 'Creates one server-ID lobby under the original player-ledger revision.' That scoping phrase distinguishes it from sibling create/join/start tools, so an agent knows this is the lobby-creation entry point rather than a join or advance-timeout call.

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' gates it on asynchronous multiplayer actions after reading horizon://docs/matches, and an explicit 'Not for' list excludes polling, page traversal, timeout progression, invented winners and automatic rewards. It also names concrete alternatives (horizon_get_matches, horizon_get_match for reconciliation, horizon_signin_email / horizon_signin_anonymous for the session, horizon_test_connection for key diagnostics).

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