Skip to main content
Glama

get_server_logs

Read-only

Fetch production Roblox game-server logs with full error and warning stack traces by jobId, or list running servers to pick one. Use it to diagnose live game issues and crashes.

Instructions

Recent PRODUCTION game-server logs (errors/warnings with full stack traces) via the Open Cloud Server Management API (Game Server Logs, BETA) — per-server visibility into your LIVE game, the same data as Creator Hub → Server Management → Logs tab. Logs take ~3 min to appear after they're emitted. Pass serverId (a jobId, same as game.JobId) to read one server's logs; omit it to list the currently running servers so you can pick one (re-call with serverId). Server-emitted duplicates are aggregated into skippedCount. Needs TUFAN_OPENCLOUD_KEY with the universe read scope. Siblings: get_output_log = edit-mode Studio Output; get_recent_errors = live Studio session feed; this = PRODUCTION servers. Pair with get_server_history to find terminated/crashed servers (logs stay readable after shutdown).

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": "get_server_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNomax log entries per page (default 25, max 100)
placeNoTarget place (PlaceId or project name). Defaults to the bound/sole connected place.
cursorNoPageToken from a previous call's nextPageToken
filterNoraw CEL filter override (e.g. 'severity >= 2'), replaces the severity filter
versionNoplace version number (default: latest published version, auto-resolved)
serverIdNojobId of the server to read logs from (omit to list running servers first)
severityNoonly logs of this severity (server logs are currently errors/warnings only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only say readOnly and open-world; the description adds real operational context: ~3 min ingestion delay, TUFAN_OPENCLOUD_KEY with universe read scope required, duplicates collapsed into skippedCount, and that logs remain readable after shutdown. Missing only pagination/failure behavior, which the cursor param implies but the text does not discuss.

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?

Front-loaded with the resource and scope, then procedure, then constraints, then sibling disambiguation — a sensible ordering. It is a dense single block with heavy em-dash use, but nearly every clause carries non-obvious information, so little is expendable.

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?

For a 7-parameter, zero-required, no-output-schema read tool, the description covers the data source, latency, auth scope, dedup behavior, the two-phase invocation pattern, and cross-tool navigation. Nothing an agent needs to invoke it correctly is absent.

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 is 3, but the description adds meaning beyond it: serverId is a jobId equivalent to game.JobId, and omitting it changes the tool's behavior into a server-listing call. The filter-vs-severity interaction is left to the schema, so it is not a full 5.

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?

States a specific verb and resource — read PRODUCTION game-server logs (errors/warnings with stack traces) via the Open Cloud Server Management API — and explicitly names the three sibling tools it is not (get_output_log = edit-mode Studio, get_recent_errors = live Studio session, this = production servers). An agent can route correctly without opening the 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?

Gives an explicit two-phase procedure: omit serverId to list currently running servers, then re-call with serverId to read one. It also states when to pair with get_server_history for terminated/crashed servers, and where the same data lives in the UI, which is genuine when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.