Skip to main content
Glama

Dashboard

glitchless_dashboard
Read-onlyIdempotent

The 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

NameRequiredDescriptionDefault
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.
pageNoId of the board page to evaluate (default: the first board)
guideNoInstead of reading the dashboard: how to design one for this game, step by step (the Glitchless plugin's dashboard skill)
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.
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
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
    • addedInput schema / properties / guide
      Added value: +{
      +  "description": "Instead of reading the dashboard: how to design one for this game, step by step (the Glitchless plugin's dashboard skill)",
      +  "type": "boolean"
      +}
  2. 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."
  3. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, yet the description still adds substantive traits: money panels are filtered so amounts sent in another currency are dropped and listed in `mismatch`, Robux devex is an estimate in USD and 'never money', and guide mode returns up to 45,000 characters. It also flags that the answer reports when the data window starts later than requested. What is missing is any sense of result size, pagination across pages/boards, or cost of the call.

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 content is compressed into a single dense run-on paragraph of chained parentheticals, mixing input parameters with response fields and burying the important guide:true behavior at the end. Individual clauses are information-bearing, but the lack of segmentation makes the definition hard to parse on a quick read, which is exactly when an agent selects a tool.

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 10-parameter tool with no output schema, the description does the heavy lifting on the response shape: page/board structure, `source`, `spec` for editing and sending back, money/currency semantics, and branding. It also covers the alternate guide mode. The main omission is how much of the dashboard comes back at once and whether pages/boards must be fetched one at a time.

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

Parameters2/5

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

Schema coverage is 100%, so the schema already carries the parameter documentation, and the description adds little for actual inputs — most of its prose (`source`, `spec`, `currency`, `mismatch`, `devex`, `brand`) describes response fields, not parameters. Worse, it refers to a `where` argument that does not exist in the schema; the corresponding parameter is named `props`. That mismatch can send an agent looking for a nonexistent field.

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 names a specific resource and its structure: the dashboard's pages in order, each a board (panels) or a built-in view, plus one board's panels with their numbers for the window. That is far more concrete than the name alone. The gap is that the verb is elliptical — it never says 'read' or 'get', so the agent must infer the operation from context, and the mention of built-in views (events, performance, errors, servers) blurs the line with sibling tools of those names.

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?

One explicit directive is given: 'Read it before a first glitchless_set_dashboard', plus the guide:true alternative for designing a dashboard. Beyond that, there is no guidance on when to prefer this tool over the sibling tools that cover the same subjects (glitchless_performance, glitchless_events, glitchless_servers) even though the description lists those as built-in dashboard views. Usage is implied rather than routed.

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