Skip to main content
Glama

open_game

Creates a per-game workspace and imports a game file as a read-only original plus a working copy, optionally loading a profile for subsequent modding tasks.

Instructions

Open (or create) a per-game workspace.

Use this first before any other tool. Imports source_path into the workspace as a read-only original + working copy. Optionally load a game profile dir.

Args: game_name: Short identifier for the game (e.g. "mygame_v1"). source_path: Path to the game file to import (exe/apk/save). Optional. profile_dir: Path to a profile/adaptor folder. Optional.

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": {
      "game_name": "<game_name>"
    },
    "name": "open_game"
  }
}

Input Schema

NameRequiredDescriptionDefault
game_nameYes
profile_dirNo
source_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations at all, the description bears the full behavioral burden. It usefully discloses the workspace model (read-only original + separate working copy) and that a profile directory may be loaded, but says nothing about idempotency when the game already exists, on-disk side effects, required permissions, or failure modes.

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 purpose and the ordering constraint, followed by a compact Args block; nothing is padded. The Args entries restate schema titles but each adds real semantics, so the structure earns its space.

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?

For a three-parameter entry-point tool with an output schema (so return values need not be explained), the description covers purpose, ordering, and the workspace lifecycle model well. The remaining gap is behavior on a repeated open and the effect of omitting source_path, both of which matter for a stateful setup call.

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 0%, so the description must compensate, and it does document all three parameters with real meaning: game_name as a short identifier with an example, source_path as the importable file type (exe/apk/save), and profile_dir as a profile/adaptor folder. It does not state naming constraints for game_name or what happens when source_path is omitted, so the compensation is partial rather than complete.

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 gives a specific verb and resource ('Open (or create) a per-game workspace') and immediately states the concrete effect: importing source_path as a read-only original plus a working copy. Adding 'Use this first before any other tool' positions it unambiguously against siblings such as inspect, edit, or patch_code, which operate on an already-open workspace.

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?

It states a clear precondition and ordering ('Use this first before any other tool'), which is exactly what an agent needs to sequence a workspace-scoped workflow. It doesn't name when-not to use it or what to do if a workspace already exists, but for a mandatory entry point that guidance is largely unnecessary.

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