Skip to main content
Glama

Match

glitchless_match
Read-onlyIdempotent

Matches of a multiplayer game, from every side (the game marks a match with setGroup('match', id), the ID its server made; every SDK hashes it the same way, so its players and its server join up). Without id: the window's matches, the most recent first, or the worst by lag (ping) or disconnects (sort), each with its level, players, outcomes, disconnects, ping and lag (the share of connected play over 150 ms), and its server's tick. With id: one match slot by slot (30 seconds) from its start, with a verdict that tells a whole lobby lagging at once (the server or its network) from one player lagging (their connection): each player's ping, frame time, outcome and disconnects, the server's ticks against its budget and the players connected in the same slots, and the match's events. slots: true gives every slot of every player.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "glitchless_match"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoA match id (h_… or the game's own), from the list or a finding
envNoOnly include sessions from this environment, e.g. "prod" (what the game passes to init; builds a developer runs usually send "dev")
gameNoThe game, by name or id, when signed in to a workspace (glitchless_list_games lists them); later calls keep it. With a key for one game (gl_sk_…), a call that names another game is refused: sign in to the workspace to reach every game.
sortNoWithout id: recent (default), lag (the worst ping p95 first) or disconnects
hoursNoLook-back window in hours (default 24), as far back as the workspace keeps data on Glitchless Cloud (the answer says when it starts later than asked). Past 744 (31 days) answers are by day.
limitNoWithout id: how many matches (default 20)
propsNoOnly sessions with these session properties (what the game set with setProperties): { rank: "diamond" }, or a list of values for any of them, { rank: ["diamond", "master"] }; "(none)" keeps the sessions without one. glitchless_events lists the properties and their values. Read from the sessions, so over 31 days or less
slotsNoWith id: every 30-second slot of every player and server (long for a big match); by default only the slots that lagged
serviceNoGame service name (defaults to the most recently active game)
versionNoOnly include sessions from this game version
session_typeNo"user": players only; "tester": people on TestFlight and other test builds only; "synthetic": bots, playtests and store test devices only; "all" or unset: every session. Findings (glitchless_triage, and the overview's) read the production sessions of players unless env or session_type is given
steam_branchNoOnly include sessions that ran this Steam branch ("public", or a beta's name); games that use Steamworks send it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / game / description
      Previous value: -"The game, by name or id, when signed in to a workspace (glitchless_list_games lists them); later calls keep it. Ignored with a key for one game."New value: +"The game, by name or id, when signed in to a workspace (glitchless_list_games lists them); later calls keep it. With a key for one game (gl_sk_…), a call that names another game is refused: sign in to the workspace to reach every game."
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so safety needs no repetition. Beyond that, the description discloses defaults (most recent first, 20 matches), the cost of 'slots: true' ('long for a big match'), and what the verdict is actually for (separating whole-lobby lag from one-player lag), which materially helps interpretation.

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 core distinction is front-loaded, but the prose is two very long run-on sentences loaded with nested parentheticals, which makes the id/no-id boundary harder to scan than a short structured list would. The opening parenthesis about setGroup hashing is implementation lore that does not help an agent decide or call.

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?

With 12 optional parameters, nested props, and no output schema, the description does the needed work by describing what the list and single-match responses contain (players, outcomes, disconnects, ping/lag, server tick). The framing is complete enough to call correctly; only the cross-tool routing is thin.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents id, sort, hours, limit, props, and slots in detail. The description mostly restates those semantics in prose ('Without id: the window's matches', 'slots: true gives every slot'), adding context about what the slots contain but little that isn't already in structured fields.

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 description states the resource concretely ('Matches of a multiplayer game, from every side') and immediately splits the two modes: a list of matches without an id, and a single match slot-by-slot with an id. An agent can tell this is match-level telemetry, distinct from session- or network-level siblings, though the verb is implicit rather than stated.

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

Usage Guidelines3/5

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

It clearly explains the with-id vs without-id invocation split and what each mode adds (list vs verdict/slots), which is genuine usage guidance. However, it never names when to reach for this instead of glitchless_session, glitchless_network, or glitchless_performance, all of which plausibly overlap for per-match diagnostics, leaving the choice to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources