Skip to main content
Glama

Get My Matches

horizon_get_matches
Read-onlyIdempotent

Reads the player's bounded active, invited and recent match summaries. Use when: explicit asynchronous multiplayer actions after reading horizon://docs/matches.

Instructions

Reads the player's bounded active, invited and recent match summaries. 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. Respect pollAfterSeconds on refresh. Retained state is not truncated after System Config reductions. Returns: {userId,revision,active,invites,recent,pendingResults,limits,pollAfterSeconds,serverTime}; minimal pendingResults retain matchId,finalStateRevision,ownRankedRunId and expiresAt independently of completed detail history. 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>"
    },
    "name": "horizon_get_matches"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYesActive player matching the session and project
sessionTokenYesPlayer accessToken sent only as Bearer

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.9.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already establish readOnly/idempotent/non-destructive, but the description goes well beyond them: it discloses the session-token derivation path, the pollAfterSeconds refresh contract, the fact that retained state survives System Config reductions, and per-status error semantics (404 masking, 409 conflict recovery, 422 account limits blocking create only, 401/403 auth remediation, 429 rate limiting). It also states that every failure returns an isError result with HTTP status and body.

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?

The labeled sections (Use when / Not for / Requires / Side effects / Returns / Errors) front-load the important parts and make it scannable, but the total volume is heavy for a two-parameter read call, and the errors block runs long with remediation advice that partially duplicates the 401/403/429 points. Some of it earns its place, some of it is padding.

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 full return shape ({userId,revision,active,invites,recent,pendingResults,limits,pollAfterSeconds,serverTime}) and notes the minimal pendingResults retention fields. Combined with the auth prerequisites, side effects and error contract, an agent has everything needed to call and recover from this tool.

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 two parameters are already documented; the description still adds real meaning by explaining that sessionToken must be the accessToken returned from horizon_signin_email or horizon_signin_anonymous and that the userId must be the account that signed in (403 otherwise). That operational linkage is not in the schema.

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?

"Reads the player's bounded active, invited and recent match summaries" states a specific verb (read), an exact resource (match summaries), a scope (active/invited/recent) and a boundedness constraint. It is cleanly separable from the singular horizon_get_match referenced in the same paragraph.

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?

It gives an explicit positive trigger ("Use when: explicit asynchronous multiplayer actions after reading horizon://docs/matches"), an explicit negative list ("Not for: automatic polling, page traversal, timeout progression, invented winners or automatic rewards"), and names the companion retrieval path for single matches. Little is left 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