Skip to main content
Glama

Network

glitchless_network
Read-onlyIdempotent

Network quality of a multiplayer game: ping (median and the slowest 5%), lag (the share of connected play with a round trip over 150 ms), packet loss and jitter, and disconnects (per hour played, by reason, and the share of level attempts a disconnect ended: never counted as fails), overall and by level, version, platform and kind of connection (Wi-Fi, mobile data, wired), and by region when the game sets a region property (or by any property given as by). Also the worst matches by ping (glitchless_match opens one), and the network findings: a whole lobby lagging at once (the server), one kind of connection or region lagging (players' connections, or no server near them), disconnects rising in a release. The SDKs read it from the engine's netcode (Netcode for GameObjects, Mirror, Godot's ENet, Unreal's net driver, WebRTC) or the game's netSample calls.

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

Input Schema

NameRequiredDescriptionDefault
byNoA session property to split by besides the built-in ones, e.g. "region" (the default when the game sets one) or "$play": each of its values (up to 8) read on its own
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.
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
    • 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

A3.6/5.0
Behavior4/5

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

The annotations already establish this as a safe read-only, idempotent operation. The description adds meaningful behavioral context beyond annotations: it explains how disconnects are counted, how lag can be interpreted as server-side versus player-side, and where the SDKs source the data from.

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 front-loaded with the core purpose and metrics, but it is delivered as one very long, heavily punctuated sentence. It is information-dense and mostly earns its place, yet the run-on structure makes it harder to parse than necessary.

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 complex nine-parameter analytics query with no output schema, the description covers the main metrics, groupings, findings, and data sources well. It does not fully specify the response shape, but the core semantics needed to invoke and interpret the tool are present.

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

Parameters3/5

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

Schema description coverage is 100%, so the input schema already documents the parameters thoroughly. The description reinforces the `by` behavior and built-in breakdowns but does not add syntax or format details beyond what the schema provides.

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 clearly identifies the resource as multiplayer network quality and enumerates the concrete metrics: ping, lag, packet loss, jitter, and disconnects. It also states the major breakdowns and findings, so the tool is distinguishable from generic session, performance, or server tools, though it does not explicitly contrast itself with all siblings.

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?

Usage is implied through the metric set and the note that glitchless_match opens one of the worst matches. There is no explicit when-to-use or when-not-to-use guidance against alternatives such as glitchless_performance, glitchless_servers, or glitchless_triage.

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