Skip to main content
Glama

run_tga2skybox

Builds a cubemap .vtf from six TGA faces and writes both LDR and HDR sets, creating a skybox from images without running the map in-engine. Reads and writes only in the faces' directory.

Instructions

Builds a cubemap .vtf from six TGA faces -- rt.tga, lf, bk, ft, up, dn -- and writes both the LDR and the HDR set. This is the one part of cubemap work that does NOT need the engine: buildcubemaps captures a cubemap from inside a running map, this makes one from images. Drives ficool2's tga2skybox, a separate download; health says whether it is installed. Reads and writes only in the directory the faces are in.

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": {
      "dir": "<dir>",
      "base": "<base>"
    },
    "name": "run_tga2skybox"
  }
}

Input Schema

NameRequiredDescriptionDefault
dirYesDirectory holding the six TGA faces. The .vtf files are written here too.
baseYesName shared by the faces: `sky_x` for sky_xrt.tga ... sky_xdn.tga.
confirmNoRequired (true) to run this tool: it writes or executes.

Output Schema

NameRequiredDescriptionDefault
okYes
dirYes
vtfYes
baseYes
noteYes
toolYes
bytesYes
facesYes
hdrVtfYes
headerYes
writtenYes
exitCodeYes
hdrBytesYes
hdrHeaderYes
stdoutTailYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.24-alpha

TDQS

A4.1/5.0
Behavior4/5

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

Annotations carry only a title, so the description does the heavy lifting and does it well: it discloses that both LDR and HDR sets are written, that it shells out to a separate third-party download (ficool2's tga2skybox) whose presence health can report, and that reads/writes are confined to the faces directory. It does not say what happens on failure or whether existing .vtf outputs are overwritten.

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?

Three front-loaded sentences: purpose first, then the sibling contrast, then dependency and filesystem constraints. Dense but every sentence earns its place; the inline '-- <base>rt.tga, lf, bk, ft, up, dn --' list is slightly compressed but still readable.

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 file-writing tool with an output schema, the description covers inputs, external dependency, install verification, and path scoping. The only gap is error/overwrite behavior, which the output schema may partially address.

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 the schema already explains dir, base (with a sky_xrt.tga example), and confirm. The description restates the face-suffix convention and the directory scoping, which reinforces but adds little genuinely new meaning beyond the structured fields.

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 and resource: builds a cubemap .vtf from six TGA faces, enumerating the face naming convention. It also explicitly separates itself from buildcubemaps ('captures a cubemap from inside a running map, this makes one from images'), so an agent can distinguish the two without opening a schema.

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 context for when to use it: cubemap work that does NOT need the engine, contrasted with buildcubemaps, plus a pointer to health to verify the external tga2skybox dependency before calling. There is no explicit failure or exclusion guidance beyond that contrast, which keeps it short of a 5.

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