Skip to main content
Glama
ProjectMakersDE

horizOn MCP Server

Official
by ProjectMakersDE
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Match

horizon_get_match
Read-onlyIdempotent

Reads one authorized multiplayer match snapshot by ID for explicit asynchronous actions, returning match state, poll timing, and server time.

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. 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).

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
Behavior5/5

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

Well beyond the annotations: it discloses what invited players versus participants actually receive (dataBase64=null lobby metadata vs original bytes and reports), the exact return shape, and a full error taxonomy — 404 intentional masking, 409 REVISION/STATE_CONFLICT with a do-not-resubmit rule, RESULT_CONFLICT preservation, RUN_EXPIRED, 501 for simpleServer ranked, 401 vs 403 session distinctions, and 429 rate limiting.

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?

Front-loaded with labeled sections (Use when / Not for / Requires / Side effects / Returns / Errors), which makes a long description scannable. It loses a point for redundancy — the 401 and rate-limit guidance is restated in the Requires, Errors and closing failure paragraph.

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, so the explicit "Returns: {match,pollAfterSeconds,serverTime}" is load-bearing, and the auth prerequisite, HORIZON_API_KEY requirement, and every failure mode an agent could hit are covered. Nothing needed to invoke 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 real meaning: sessionToken must come from horizon_signin_email/horizon_signin_anonymous as an accessToken sent as Bearer, and the 403 note explains that userId must be the same user who signed in. That turns three plain UUID/string fields into a coherent auth contract.

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?

"Reads one currently authorized match snapshot" gives a specific verb (read) plus resource and cardinality (one match), which cleanly separates it from horizon_get_matches. The only weakness is the self-referential "Reconcile with horizon_get_matches and horizon_get_match", where the singular name is the tool itself, slightly blurring the sibling boundary.

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) plus an explicit "Not for" list covering automatic polling, page traversal, timeout progression, invented winners and automatic rewards. That is a genuine when/when-not statement with named alternatives (horizon_get_matches, and by contrast horizon_advance_match_timeout / horizon_submit_match_turn).

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