Skip to main content
Glama

Get Match

horizon_get_match
Read-onlyIdempotent

Reads one currently authorized match snapshot. Use when: explicit asynchronous multiplayer actions after reading horizon://docs/matches.

Instructions

Reads one currently authorized match snapshot. 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: Read only. Invited players receive lobby metadata with dataBase64=null, participants receive original bytes and reports. Returns: {match,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>",
      "matchId": "<matchId>"
    },
    "name": "horizon_get_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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.9.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, but the description adds real behavior beyond them: what each recipient sees (invited players get dataBase64=null lobby metadata, participants get original bytes and reports), the granted revision semantics on 409, and that ranked runs are never replaceable. It loses a point only for the vague, self-referential 'Reconcile with horizon_get_matches and horizon_get_match' line, which does not clarify anything actionable.

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

Conciseness3/5

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

Front-loaded and sectioned (Use when / Not for / Requires / Side effects / Returns / Errors), but the Errors block is an undifferentiated wall of codes and the sentence 'Consent and game consensus do not validate honest gameplay' is a non-sequitur that does not help invocation. The self-reference to horizon_get_match as a reconciliation target is also confusing.

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?

With no output schema, the description supplies the return shape {match,pollAfterSeconds,serverTime}, auth prerequisites including HORIZON_API_KEY, and per-status remediation for 401/403/404/409/422/429/501. Nothing essential to calling this read tool correctly appears 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; the description earns extra credit by giving the sessionToken provenance — sign in with horizon_signin_email or horizon_signin_anonymous and pass the resulting accessToken — and by tying the 403 case to 'pass the userId that signed in', which links userId to session identity. It adds meaning the schema alone does not convey.

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 with scope: 'Reads one currently authorized match snapshot.' The single-match read is clearly separated from the list sibling via 'Reconcile with horizon_get_matches', so an agent can route between them without opening a schema.

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' clause plus a concrete 'Not for' exclusion list (automatic polling, page traversal, timeout progression, invented winners, automatic rewards). It also names the correct sibling to reconcile against when a list view is needed, leaving little to inference.

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