Skip to main content
Glama

Download session artifacts

gameye_get_artifacts
Idempotent

Download a file or directory such as crash dumps, replays, or logs from a session container; returns an uncompressed tar archive saved to a private temp directory with its local path.

Instructions

Download a file or directory (crash dumps, replays, logs) from a session's container. The server returns an uncompressed tar archive, saved to a new private temp directory; the local path is returned. 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": {
      "session": "<session>",
      "path": "<path>"
    },
    "name": "gameye_get_artifacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute path inside the container to export, e.g. /app/logs or /tmp/crash.dmp
sessionYesSession ID to download artifacts from

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.3

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), yet the description still adds real value: the response is an uncompressed tar archive, the local write goes to a new private temp directory, and the local path is returned. It also discloses the auth requirement and the specific fallback behavior when GAMEYE_API_TOKEN is missing, which no structured field conveys.

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 tight sentences: purpose first, return mechanics second, auth behavior third. Front-loaded, no filler, and every clause contributes information an agent would otherwise have to guess.

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 two-parameter tool with no output schema and full schema coverage, the definition covers what is downloaded, what comes back, where it lands, and how auth failure is handled. Nothing an agent needs in order to call it correctly 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 coverage is 100% and both parameters carry descriptions plus an absolute-path pattern, so the schema does the work. The description adds only mild extra meaning by clarifying a directory may be exported and by naming artifact types likely to be addressed via 'path'.

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: 'Download a file or directory ... from a session's container', and illustrates with crash dumps, replays, logs. It doesn't name or contrast with gameye_get_logs, whose territory overlaps the 'logs' example, so the sibling boundary is left slightly blurry.

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 context is implied by the artifact examples and the download framing, but there is no explicit when-to-use/when-not guidance and no named alternative for fetching logs or session details. The auth note is a precondition rather than routing guidance.

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