Skip to main content
Glama

get_server_history

Read-only

Retrieve a rolling 30-day history of published game servers, including active and terminated instances with status, uptime, termination reason, and last-known memory, FPS, and occupancy.

Instructions

Server History for your PUBLISHED game via the Open Cloud Server Management API (BETA) — a rolling 30-day list of active AND terminated servers (shut down / restarted / crashed / out_of_memory / moderated) with status, uptime, termination time, last-known memory/fps/occupancy. Default view is terminated servers only; pass status:active for live servers or status:all for everything. This is the same ListGameServers endpoint Creator Hub's Server Management page uses. 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. Follow up with get_server_logs serverId: to read a server's errors/stack traces (logs remain available after termination).

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

Input Schema

NameRequiredDescriptionDefault
limitNomax servers 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, replaces the status filter
statusNostatus filter: "terminated" (default) = every non-active status, "all" = no filter, or one specific status
orderByNosort field, e.g. "uptime" or "uptime desc" (single field)
versionNoplace version number (default: latest published version, auto-resolved)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say readOnlyHint and openWorldHint; the description adds the 30-day rolling retention window, the enumerated termination causes, the returned fields, and the non-obvious fact that logs remain available after termination. It also discloses the auth requirement (TUFAN_OPENCLOUD_KEY with universe read scope), which is the main failure mode for this call.

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?

The description is front-loaded with the resource and scope, then defaults, then siblings, then follow-up — a sensible ordering with no filler. It is dense and somewhat run-on (one em-dash chain carries most of the content), which costs a point on readability but not on value.

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?

With no output schema, the description compensates by naming the returned fields (status, uptime, termination time, last-known memory/fps/occupancy). Auth scope, default filtering, and the natural next tool are all covered, leaving nothing an agent needs before invoking it.

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 the baseline is 3; the description nonetheless adds interpretive meaning by explaining that the default 'terminated' view aggregates every non-active status (shut down / restarted / crashed / out_of_memory / moderated), which changes how an agent should read results. It does not mention the filter override, orderBy, or cursor interplay, so it stops short of full parameter guidance.

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 verb and resource ('rolling 30-day list of active AND terminated servers') and pins the exact underlying endpoint (ListGameServers). It explicitly differentiates itself from get_output_log (edit-mode Studio) and get_recent_errors (live Studio session) by declaring 'this = PRODUCTION servers', so an agent can route without opening any 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?

It states the default behavior ('terminated servers only'), the conditions that change it ('pass status:active for live servers or status:all for everything'), and names the sibling alternatives with their respective domains. It also prescribes a follow-up call (get_server_logs with serverId:<jobId>), which is actionable when-to-use guidance rather than mere context.

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