Skip to main content
Glama

Find Open Matches

horizon_find_open_matches
Read-onlyIdempotent

Reads one strength-filtered page of open asynchronous multiplayer matches with active-owner checks, returning candidates, a cursor, and poll timing for explicit matchmaking.

Instructions

Reads one strength-filtered open-lobby page under current blocks and active-owner checks. 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, at most256 metadata candidates and50 results. Empty cursor pages are valid. No game state is returned. Returns: {matches,nextCursor,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
limitNoOne explicit page of at most fifty summaries
cursorNoPrevious consumed-only cursor; an empty page can have a continuation
userIdYesActive player matching the session and project
maxStrengthYesExact safe integer strength from the original search range
minStrengthYesExact safe integer strength from the original search range
sessionTokenYesPlayer accessToken sent only as Bearer

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?

Annotations already mark this as read-only and idempotent, and the description reinforces that with 'Side effects: Read only' and 'No game state is returned.' It adds substantial context beyond annotations: auth requirements, candidate/result limits, cursor semantics, rate limits, and a detailed error taxonomy.

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?

The description is long but well structured and front-loaded: purpose first, then use/not-for guidance, prerequisites, side effects, return shape, and errors. The error section is dense and somewhat expansive, but it remains relevant to correct invocation and troubleshooting.

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, but the description fully documents the return shape as {matches,nextCursor,pollAfterSeconds,serverTime}. It also covers auth, read-only behavior, pagination limits, valid empty pages, and relevant error paths, making it complete for this complex 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 baseline is 3, but the description adds useful meaning by linking sessionToken to the accessToken from sign-in and requiring userId to match the signed-in player. It also frames minStrength and maxStrength as a strength-filtered lobby query, though those parameters are still mostly explained by 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?

The description opens with a specific verb and resource: it reads one strength-filtered open-lobby page under current blocks and active-owner checks. That distinguishes it from broader match retrieval siblings such as horizon_get_matches and horizon_get_match.

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 explicitly gives a 'Use when' condition tied to asynchronous multiplayer actions after reading the matches docs, and a 'Not for' list covering polling, page traversal, timeout progression, invented winners, and automatic rewards. It also directs reconciliation with horizon_get_matches and horizon_get_match.

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