Skip to main content
Glama

Get Match Limits

horizon_get_match_limits
Read-onlyIdempotent

Reads the player's five-tier limits and project capabilities. Use when: explicit asynchronous multiplayer actions after reading horizon://docs/matches.

Instructions

Reads the player's five-tier limits and project capabilities. 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: {limits,config,capabilities,pollAfterSeconds,serverTime}; limits include activeMatches,stateBytes,retainedMatches,pendingInvites,settlementMatches,historyRetentionSeconds,rankedSettlementSeconds. Zero completed history is valid. 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_match_limits"
  }
}

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.2/5.0
Behavior4/5

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

The annotations already cover read-only/idempotent/non-destructive, but the description adds substantial context they cannot: the required signin flow and sessionToken provenance, the pollAfterSeconds refresh contract, that retained state survives System Config reductions, and per-status error semantics (404 privacy hiding, 422 ACCOUNT_MATCH_LIMIT_REACHED blocking create only, 429 per-minute rate limit, 501 for simpleServer ranked). Remaining gap: no statement about response size or whether the call itself counts against any limit.

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?

It is well front-loaded with labeled sections (Use when, Not for, Requires, Side effects, Returns, Errors), so it scans easily. However, the error block enumerates conditions that cannot arise from a read-only limits read (409 REVISION_CONFLICT/STATE_CONFLICT, RESULT_CONFLICT, RUN_EXPIRED/RUN_ALREADY_USED), which dilutes focus and makes the definition roughly twice the length needed for this call.

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, and the description compensates by enumerating the returned envelope (limits, config, capabilities, pollAfterSeconds, serverTime) and the specific limit keys such as activeMatches, stateBytes, retainedMatches, pendingInvites, settlementMatches, and the two retention windows. Authentication, refresh behavior, and failure modes are all covered, so an agent has everything needed to invoke and interpret the call.

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 by tying userId to the identity that signed in and sessionToken to the accessToken issued by horizon_signin_email/horizon_signin_anonymous sent as a Bearer token. That clarifies the otherwise easy-to-miss requirement that userId must match the token's owner.

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 the player's five-tier limits and project capabilities" gives a concrete verb plus the exact resources returned, so an agent knows this is a quota/capability read rather than a match read. It is distinguishable from horizon_get_matches and horizon_get_match, which it names for reconciliation, but it does not distinguish itself from the other limits tools (chat, marketplace) in the sibling set.

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 the docs resource) plus an explicit "Not for" list covering automatic polling, page traversal, timeout progression, and invented winners/rewards. It also names the reconciliation targets horizon_get_matches and horizon_get_match, and adds the caution that consent and game consensus do not validate honest gameplay.

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