Triage
glitchless_triageRanked findings for a game, after its headline numbers (sessions, players, crash-free and error-free sessions, frame-time p50/p95/p99 and the share of frames over their own screen's budget, pct_frames_over_budget, with frame_budgets the share of play at each refresh rate; hitches a minute, rage quits) and the versions deployed in the window: performance spikes per level (with the gauges, counter bursts and events they correlate with), memory leaks, top errors, difficulty spikes / rage-quit hotspots, walls (a level, or one value of a level start's attribute such as a tier), version regressions, settings that run slow (a session property), the network (a whole lobby lagging at once: the server; one kind of connection, platform or region lagging; disconnects rising in a release) and the game's dedicated servers (falling behind when full, a crash that ends matches, memory that keeps climbing) — ranked by severity and player impact, each with evidence and a suggested fix, and naming a session property when most of a problem falls on one value. Findings the game's owner marked known (glitchless_mark_known) come after the rest with known and its note: accepted, not new. One that got worse since has came_back instead. Errors the owner resolved (glitchless_resolve_error) have no finding, unless one came back in a later version: then its finding has came_back with the version and the note. Start here when asked 'what's wrong with my game?'.
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_triage"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| env | No | Only include sessions from this environment, e.g. "prod" (what the game passes to init; builds a developer runs usually send "dev") | |
| game | No | 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. | |
| hours | No | Look-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. | |
| props | No | Only 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 | |
| service | No | Game service name (defaults to the most recently active game) | |
| version | No | Only include sessions from this game version | |
| session_type | No | "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_branch | No | Only include sessions that ran this Steam branch ("public", or a beta's name); games that use Steamworks send it |