Skip to main content
Glama

Servers

glitchless_servers
Read-onlyIdempotent

A multiplayer game's dedicated servers, when they run the Glitchless SDK in server mode (Node glitchless/server, or the Unity, Godot or Unreal server role): servers running now and the players connected to them; tick time against its budget (the slowest 5% of ticks, and the share of windows over budget) by players connected, by map and by version; CPU, memory and networked objects; crashes, each with the matches it ended and the players it dropped; long-running servers whose memory or objects keep climbing; the latest server runs; and the server findings (falling behind when full, a crash that ends matches, a leak). A server's sessions are kept apart from players' under the companion service ".server": every other tool reads them with service ".server" (glitchless_session for one server run, glitchless_get_error for a server crash's stack). Server sessions count as sessions like any other.

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

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.
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?

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is free. The description earns credit by disclosing a behavior annotations cannot: server sessions are partitioned under a companion service "<game>.server" and other tools must pass that service name to reach them, plus the note that server sessions count as sessions like any other. That is genuinely non-obvious cross-tool context.

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 first sentence is a single sprawling clause chaining roughly a dozen output categories with semicolons, which is hard to scan and buries the most actionable fact (the companion service name) at the end. Every clause is substantive content, but the structure is a data dump rather than front-loaded guidance.

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 an 8-parameter, no-output-schema read tool, the description covers the return surface thoroughly (current servers, tick budget percentiles, resource usage, crashes with affected matches, leaks, recent runs, findings) and explains the service-splitting convention that would otherwise cause failed follow-up calls. Nothing critical about invoking the tool is missing.

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 every parameter already carries its own documentation (env, hours caps, props semantics, service, session_type enum). The description adds no parameter-level meaning beyond that baseline, which is acceptable but not additive.

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 clause pins down the resource precisely – dedicated servers running the Glitchless SDK in server mode (Node glitchless/server or Unity/Godot/Unreal server roles) – and the rest enumerates the specific signals returned (tick time vs budget, CPU/memory, crashes, leaks, findings). This is far more specific than a bare name restatement, though it reads as a data-catalog inventory rather than a single crisp verb.

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 rather than stated: an agent can infer this is the server-telemetry entry point and that glitchless_session and glitchless_get_error drill into individual server runs and crash stacks. However, it never says when to pick this over glitchless_performance or glitchless_network, which overlap on the same CPU/memory/tick metrics, leaving a real routing ambiguity.

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