Skip to main content
Glama

Get session logs

gameye_get_logs
Read-onlyIdempotent

Fetch a snapshot of stdout/stderr logs from a Gameye session to troubleshoot server output. The MCP response includes the last 50,000 characters; call again for newer output.

Instructions

Fetch a snapshot of stdout/stderr logs from a Gameye session (the last 50,000 characters). Live streaming is not available through MCP; call again to see newer output. Needs GAMEYE_API_TOKEN; without one, returns setup steps and sends nothing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "gameye_get_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSession ID to fetch logs for
followNoIgnored: MCP is request/response, so a snapshot is always fetched. Call again to see newer output.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.3

TDQS

A4.1/5.0
Behavior5/5

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

Goes well past the annotations by disclosing the 50,000-character truncation, the absence of live streaming, the GAMEYE_API_TOKEN requirement, and the failure mode where a missing token returns setup steps and sends nothing. These are exactly the behavioral traits an agent needs and that annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with what is returned and how much, followed by the polling model and the auth prerequisite. No redundancy or filler.

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?

There is no output schema, yet the description conveys the essential return characteristics (stdout/stderr snapshot, capped at 50,000 characters) and the auth prerequisite. It stops short of saying how the log payload is shaped or delimited, which would help an agent parse the result.

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 both 'id' and 'follow' are already documented in structured data, including the fact that 'follow' is ignored. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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?

States a specific verb and resource ('Fetch a snapshot of stdout/stderr logs from a Gameye session') plus a concrete scope qualifier (last 50,000 characters). It never names a sibling such as gameye_get_artifacts to draw the logs-vs-artifacts boundary, so an agent must infer that distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear operational guidance: live streaming is unavailable, so poll by calling again to see newer output. It does not state when a caller should prefer a related tool (e.g., artifacts or session description) over logs, but the usage model is unambiguous for the tool itself.

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