Skip to main content
Glama

Events

glitchless_events
Read-onlyIdempotent

The game's own metrics, from the custom events it sends with track() and the streams it counts with count() (marked counted: summed on the device per window, so their numbers have sums and averages but no spread): each event's count in the window, the sessions and players that sent it, how its attribute values break down (for example plays by mode, paywall views by placement, purchases started vs done; a list attribute such as a deck by element, each event counted once under each), the sums of its numeric attributes per currency (revenue: the amount of purchase events) and their p50, p90 and p99, and hours, the hours played in the window, to turn any count into a rate per hour. Give funnel to count the sessions that went from one event to the next, in that order. With name and rate (a flag such as "won", or a word outcome "result=win") or avg (a numeric attribute), it measures that event: overall, or with by per value (win rate by hero, with a 95% interval for each, next to the overall rate). With name and of (a numeric attribute), it gives that attribute's distribution: percentiles and a histogram, optionally by a split. With name and first, when sessions first sent it: the median and p90 seconds from a session's start to its first one (time in the lobby before first leaving it), and the share of ended sessions that never sent it (31 days or less). properties lists what the game set for its sessions with setProperties (rank, class, region, a preset), each with its values and their sessions and players; identifier_like marks one with more than 200 values a day, which is an ID rather than a property. Every read tool filters by them (props) and splits by them (by "$rank"). By default each attribute shows its top 5 values (a numeric one its average and percentiles) and each property its top 5: detail: true gives every value with its sessions.

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

Input Schema

NameRequiredDescriptionDefault
byNoWith rate, avg or of: split by an attribute (a list splits by element), $version, $level, $zone, $platform, $browser, $device_tier, $link (the kind of connection), $graphics (the graphics setting), $site (where a web game was played: itch.io, its own site…), or a session property ("$rank")
ofNoA numeric attribute whose distribution to give, e.g. "duration_s" (match length) or "placement"
avgNoA numeric attribute's mean per event, e.g. "duration_s"
envNoOnly include sessions from this environment, e.g. "prod" (what the game passes to init; builds a developer runs usually send "dev")
minNoWith rate or avg and by: the fewest events a row needs (default 30 for a rate, 10 for an average); smaller rows are counted in small
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.
nameNoOnly this event, e.g. "paywall". With rate, avg or of, the event to measure; it can carry a filter like a panel's event: "match_end:mode=ranked", or "battle_end:deck=hog_rider+ice_spirit" for decks with both
rateNoThe share of the event's events where a flag holds ("won": true or false, or 1 or 0) or a word outcome holds ("result=win")
firstNoWith name: the seconds from each session's start to its first such event (median_s, p90_s, over the sessions that sent it) and the ended sessions that never sent it (never, ended, never_pct). For a lobby: how long players stay before first leaving, and how many never leave. Works for events a Roblox server sends for a player
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
detailNoEvery value of every attribute and property, with its sessions (default: the top 5 of each)
funnelNoSteps in order, comma-separated: "open,paywall,buy". A step can require a value: "buy=done" (any attribute) or "buy:step=done"; a list matches when it has the value
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 / by / description
      Previous value: -"With rate, avg or of: split by an attribute (a list splits by element), $version, $level, $zone, $platform, $browser, $device_tier, $link (the kind of connection), $graphics (the graphics setting), or a session property (\"$rank\")"New value: +"With rate, avg or of: split by an attribute (a list splits by element), $version, $level, $zone, $platform, $browser, $device_tier, $link (the kind of connection), $graphics (the graphics setting), $site (where a web game was played: itch.io, its own site…), or a session property (\"$rank\")"
  2. Changed1 schema field changed
    • changedInput schema / properties / by / description
      Previous value: -"With rate, avg or of: split by an attribute (a list splits by element), $version, $level, $zone, $platform, $browser, $device_tier, $link (the kind of connection), or a session property (\"$rank\")"New value: +"With rate, avg or of: split by an attribute (a list splits by element), $version, $level, $zone, $platform, $browser, $device_tier, $link (the kind of connection), $graphics (the graphics setting), or a session property (\"$rank\")"
  3. 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."
  4. Changed2 schema fields changed
    • addedInput schema / properties / detail
      Added value: +{
      +  "description": "Every value of every attribute and property, with its sessions (default: the top 5 of each)",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / first
      Added value: +{
      +  "description": "With name: the seconds from each session's start to its first such event (median_s, p90_s, over the sessions that sent it) and the ended sessions that never sent it (never, ended, never_pct). For a lobby: how long players stay before first leaving, and how many never leave. Works for events a Roblox server sends for a player",
      +  "type": "boolean"
      +}
  5. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, and the description adds substantial context beyond them: default top-5 truncation, `detail: true` full values, default 24h window and 9600h max, retention caveats, `min` thresholds (30 for rate, 10 for average), and `identifier_like` >200 values/day. No statement conflicts with the annotations.

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 description is information-dense and front-loads the core purpose, but it is a single long paragraph with semicolon-heavy clauses that is hard to scan for a 17-parameter tool. The content mostly earns its place, yet the lack of structure (bullets or mode headings) makes it less concise in practice.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description must explain return values, and it does: counts, sessions/players, attribute breakdowns, currency sums, p50/p90/p99, funnel session counts, rate intervals, distributions/histograms, first-event median/p90/never share, and property values. It also covers defaults, retention, and filtering, making it complete for this complex tool.

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

Parameters5/5

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

With 100% schema coverage the schema already documents each parameter, but the description adds cross-parameter meaning and examples: how `by`, `of`, `avg`, `rate`, `first`, `funnel`, `props`, and `min` combine; defaults; funnel syntax; and property filtering semantics. This goes well beyond the schema's field-level descriptions.

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 opening states the resource (the game's custom events and counted streams) and enumerates the metrics returned: counts, sessions, players, attribute breakdowns, numeric sums and percentiles, and hours. It also distinguishes internal modes such as funnel, rate/avg, of, and first, though it never names sibling tools like glitchless_revenue or glitchless_player_funnel, so sibling differentiation is missing.

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 gives detailed guidance for parameter combinations: use `funnel` for ordered steps, `name` + `rate`/`avg` to measure an event, `name` + `of` for distributions, and `name` + `first` for first-event timing. However, it does not say when to choose this tool over alternatives such as glitchless_revenue or glitchless_player_funnel, nor does it provide exclusions.

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