Skip to main content
Glama

run_cubemap2hdr

Converts an LDR cubemap .vtf into the HDR version Source loads in HDR mode, producing the missing half of a map's reflection set offline without recompiling. Input must be DXT1.

Instructions

Converts an LDR cubemap .vtf into the HDR one Source loads in HDR mode, writing .hdr.vtf beside it. A map compiled without -both, or one whose cubemaps were built in LDR, renders its reflections from the LDR set in both modes; this is the offline way to produce the missing half without going back into the game. Input must be DXT1 -- the tool refuses anything else, and this says so before running. Extract one from a map with run_pakfile_extract. Drives ficool2's cubemap2hdr, a separate download; health says whether it is installed.

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": {
      "vtf": "<vtf>"
    },
    "name": "run_cubemap2hdr"
  }
}

Input Schema

NameRequiredDescriptionDefault
vtfYesPath to the LDR cubemap .vtf, absolute or repo-relative.
confirmNoRequired (true) to run this tool: it writes or executes.

Output Schema

NameRequiredDescriptionDefault
okYes
vtfYes
noteYes
toolYes
bytesYes
hdrVtfYes
headerYes
sourceYes
writtenYes
exitCodeYes
stdoutTailYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.24-alpha

TDQS

A4.6/5.0
Behavior5/5

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

Annotations carry only a title, so the description bears the full load and does: it discloses that the tool writes a file, that it hard-refuses non-DXT1 input before running, that confirm is required, and that it depends on an external ficool2 install whose presence health reports. That is exactly the mutation/dependency context an agent needs.

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?

Four sentences, each carrying real information, with the purpose and output artifact front-loaded before the rationale and constraints. Minor filler in phrases like "and this says so before running" keeps it from being maximally tight.

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?

Output schema exists so return values need not be explained, and the description still covers the prerequisite, the side effect, the failure mode, and the external dependency. Nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description earns extra credit by adding a constraint not present in the schema: the vtf path must point at a DXT1 LDR cubemap or the run is rejected. The confirm flag's purpose is left entirely to the schema.

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 ("Converts an LDR cubemap .vtf into the HDR one Source loads in HDR mode") and names the concrete output artifact (<name>.hdr.vtf written beside the input). This is clearly distinct from siblings like run_vtf_convert or run_pakfile_extract.

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?

Explains exactly the situation that calls for it: a map compiled without -both or with LDR-built cubemaps, and frames this as the offline alternative to recompiling in-game. It also points to run_pakfile_extract for obtaining input and health for checking the dependency, though it never states an explicit when-not-to-use case.

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