Dashboard
glitchless_dashboardThe game's dashboard: its pages in order, each a board (panels in the game's own terms) or a built-in view (events, performance, errors, players, heatmaps, sessions, versions, live, reports, servers, matches), and one board's panels with their numbers for the window. A board page with where shows only the sessions with those property values. page picks the board (default: the first). source says whether the dashboard was saved (by an agent or a person) or made automatically from what the game sends; spec (its pages, and its currency if it has one) is what to edit and send back to glitchless_set_dashboard. Money panels answer their currency (an ISO code, or ROBUX), and mismatch lists amounts sent in another currency, which are left out; a Robux panel with devex answers devex, an estimate in US dollars at Roblox's DevEx rate (never money). brand is the game's branding on its boards and share links: its accent colour (set with glitchless_set_dashboard's accent) and whether it has a logo and a banner (set with glitchless_set_dashboard's logo and banner, or by people in the dashboard: Edit pages → Look). With guide: true it answers instead with how to design a dashboard that fits the game: the dashboard skill of the Glitchless plugin with its example dashboards and its panels for each kind of game, for an agent without the skill (up to 45,000 characters). Read it before a first glitchless_set_dashboard.
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_dashboard"
}
}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. | |
| page | No | Id of the board page to evaluate (default: the first board) | |
| guide | No | Instead of reading the dashboard: how to design one for this game, step by step (the Glitchless plugin's dashboard skill) | |
| 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 |