Skip to main content
Glama

Get an engine's Dockerfile or shutdown-hook template

gameye_get_template
Read-onlyIdempotent

Fetches exact Dockerfile or shutdown-hook templates for Unreal, Unity, Godot, or web game servers offline, with source skill and section, no account or token needed.

Instructions

Works without a Gameye account or token. Get the Dockerfile or the shutdown-hook template for an Unreal, Unity, Godot or web game server, word for word as published in the bundled Gameye engine skill, with the skill and section it came from. Works offline. Read the rest of the skill with gameye_get_skill. If an installed copy of the Gameye skills is newer, it wins.

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": {
      "engine": "<engine>",
      "kind": "<kind>"
    },
    "name": "gameye_get_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesTemplate: dockerfile or shutdown-hook
engineYesGame server engine: unreal, unity, godot or web

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.3

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/closed-world, and the description adds genuinely new behavior: no authentication needed, offline operation, verbatim (unmodified) content, provenance metadata (skill and section), and a staleness precedence rule. None of that is recoverable from the annotations.

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-loads the most decision-relevant fact (no account/token needed) and stays to a few short sentences. Minor redundancy between 'works without a Gameye account or token' and 'works offline', but nothing is wasted overall.

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 still explains what comes back: the template word for word plus the skill and section it came from. Combined with the auth/offline and precedence notes, an agent has everything needed to call it and interpret 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 coverage is 100% with both parameters enum-constrained and described, so the schema carries the parameter burden. The description adds no per-parameter meaning beyond naming the engines and the two template kinds, which the enums already state; baseline 3 applies.

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 (Get) and resource (Dockerfile or shutdown-hook template) scoped to four named engines, and explicitly contrasts with gameye_get_skill, which returns the rest of the skill. An agent can distinguish it from siblings 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 explicit conditions: no Gameye account or token required, works offline, and use gameye_get_skill for the remainder of the skill. It also resolves a precedence conflict ('if an installed copy of the Gameye skills is newer, it wins'), which is exactly the kind of routing rule an agent needs.

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