Skip to main content
Glama

Decline Match Invitation

horizon_decline_match_invite
DestructiveIdempotent

Executes decline match invitation under the exact original revision. Use when: explicit asynchronous multiplayer actions after reading horizon://docs/matches.

Instructions

Executes decline match invitation under the exact original revision. 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: One HTTP attempt. Start requires the creator and every joined UUID exactly once. Turn requires the current unexpired actor. Timeout advances only one turn. Active leave forfeits without selecting a winner. Lobby cancel is creator-only. Full Inbox retains a durable notice without undoing a committed move. Returns: {match,pollAfterSeconds,serverTime}; departing lobby actors receive metadata only and lose point-read access. 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>",
      "expectedRevision": "<expectedRevision>"
    },
    "name": "horizon_decline_match_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYesActive player matching the session and project
matchIdYesOriginal server match UUID in the selected project
sessionTokenYesPlayer accessToken sent only as Bearer
expectedRevisionYesOriginal reviewed revision; never substitute a newer revision after an uncertain write

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.9.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructive, idempotent, non-read-only and open-world, and the description adds genuinely new context: one HTTP attempt, accessToken-as-Bearer auth, 404 obfuscation of private/missing/expired matches, 409 handling that forbids silently substituting a revision, 422/501/429/401/403 interpretations, and the note that departing lobby actors lose point-read access. The signal is diluted by side-effect sentences that describe other operations ('Start requires the creator', 'Turn requires the current unexpired actor', 'Timeout advances only one turn', 'Lobby cancel is creator-only'), which belong to sibling tools and are not this tool's behavior.

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

Conciseness2/5

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

The core action and its revision guard are front-loaded, but the body is a single dense wall of text carrying cross-tool boilerplate about start, turn, timeout, leave and cancel that does not apply to declining an invite. Roughly half the content is noise for this specific tool, forcing the agent to sift relevant error and auth rules out of unrelated match-lifecycle detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter mutation with full schema coverage and no output schema, the definition covers the pieces an agent actually needs: auth acquisition, the return shape ({match,pollAfterSeconds,serverTime}), conflict handling, and error-to-action mapping including rate limits and API-key failures. The remaining gap is that it never states the tool's own success semantics for declining (what happens to the match or invitee state), since that portion of the text was replaced by boilerplate for other operations.

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 above that by explaining where sessionToken comes from (horizon_signin_email / horizon_signin_anonymous accessToken) and by clarifying the 403 rule that userId must match the signed-in token. It reinforces rather than extends the expectedRevision meaning already stated in the schema ('never substitute a newer revision').

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?

The first sentence names a specific verb and resource ('Executes decline match invitation') and adds a distinguishing constraint ('under the exact original revision'), so an agent knows this is a revision-guarded refusal of a match invite. It does not explicitly contrast itself with the similarly named horizon_decline_group_invite or horizon_decline_friend_request, leaving the agent to infer the resource boundary from the name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The definition supplies an explicit 'Use when' condition ('explicit asynchronous multiplayer actions after reading horizon://docs/matches') and a 'Not for' exclusion list (automatic polling, page traversal, timeout progression, invented winners, automatic rewards), plus a routing hint to horizon_get_matches and horizon_get_match for reconciliation. The weakness is that the guidance is generic to all match actions rather than tailored to declining an invite, and it never states the actual precondition (an outstanding invitation to this player).

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