Skip to main content
Glama

Bug reports

glitchless_bug_reports
Read-onlyIdempotent

Bug reports players sent from inside the game (a hotkey such as F8, or a button in the game): what they wrote, the level, their position, device and version, and the session to look at with glitchless_session. Without an id: the window's reports, newest first, optionally on one level. With an id: one report with the game events just before it and the frame rate around it; add screenshot: true to see what the player saw. Several reports on one level also show up in glitchless_triage.

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_bug_reports"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoOne report, by its id from the list or from a glitchless_triage finding
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.
hoursNoLook-back window in hours (default 168, a week)
levelNoOnly reports sent on this level, e.g. "level-2"
serviceNoGame service name (defaults to the most recently active game)
versionNoOnly include sessions from this game version
screenshotNoWith id: include the player's screenshot, as an image

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

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the bar is lower, and the description still adds real information: list ordering (newest first) and the hidden enrichment returned in detail mode (game events immediately before the report plus frame rate around it). It does not state any cap on how many reports the list mode returns or how pagination works, which is the main remaining behavioral gap.

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

Conciseness4/5

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

Content is front-loaded with what a bug report contains, then the two modes, then the screenshot toggle and sibling cross-references. It is a single dense paragraph that is somewhat long, but nearly every clause carries information; the in-game hotkey aside (F8) is the only mildly expendable 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?

With no output schema and seven parameters, the description must carry the return-shape burden, and it does for both modes, including the screenshot image case. It falls short on volume and pagination expectations for the list mode, which an agent needs to avoid assuming it received all reports in the window.

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 baseline would be 3, but the description adds cross-parameter semantics the schema cannot express: that `id` switches the tool from a list to a single-report view, that `screenshot` only has meaning together with `id`, and that `level` narrows the list window rather than the detail view. That is genuine added meaning beyond the field-level descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (bug reports submitted by players from inside the game) and enumerates its payload: player text, level, position, device, version, and linked session. It also splits the two operating modes (no id = list, with id = single enriched report) and names the sibling tools that overlap (glitchless_session, glitchless_triage), so an agent can place it among siblings without opening a schema.

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

Usage Guidelines5/5

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

"Without an id: the window's reports... With an id: one report..." gives explicit branching on the key parameter, and "add screenshot: true" states the follow-up action needed for image retrieval. It also routes the agent elsewhere by noting the related session tool for session drill-down and glitchless_triage for cross-report level views.

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