Skip to main content
Glama

write_vmf

Creates an empty .vmf map with a worldspawn skyname for Hammer, refusing to overwrite existing files so other map writers have the base file they expect.

Instructions

Creates an empty .vmf: Hammer's File > New. The map every other writer here assumes already exists -- write_vmf_solid reads its target before writing and refuses a file with no world block, so neither an absent nor an empty file is a place to start. Writes worldspawn with a skyname, because a map without one renders whatever sky the engine loaded last. REFUSES to overwrite: a map is hours of work and this tool's whole job is the first second of it.

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": {
      "path": "<path>"
    },
    "name": "write_vmf"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameNoGame profile id. This fork supports only 'l4d2', which is also the default; any other id is refused rather than answered about the wrong game.
pathYesWhere to create the .vmf, absolute or relative to the repo root.
dryRunNoCheck and report without writing. Every verification runs either way.
confirmNoRequired (true) to run this tool: it writes or executes.
skynameNoworldspawn's skyname. read_game_content lists what the game has.sky_l4d_c1_1
gridSpacingNoThe grid an editor opens the file showing. Cosmetic; nothing compiles from it.

Output Schema

NameRequiredDescriptionDefault
noteYes
pathYes
bytesYes
dryRunYes
skyboxYes
skynameYes
writtenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.24-alpha

TDQS

A4.5/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 bears the behavioral burden and does well: it discloses that a worldspawn with a skyname is written, that the tool refuses to overwrite, and why (the sky default prevents stale engine state). It omits the confirm/dryRun safety mechanics that live in the schema, but the destructive-refusal behavior is clearly stated.

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?

The defining action is front-loaded in the first clause, and the prerequisite and refusal constraints follow in a logical order. The closing aphorism ("a map is hours of work and this tool's whole job is the first second of it") is characterful but slightly padded.

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?

With an output schema and full schema description coverage, the definition only needs to cover purpose, prerequisites, and refusal policy, all of which are present. Nothing an agent needs in order to call it correctly appears to be 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; the description earns more by explaining the skyname's purpose ("a map without one renders whatever sky the engine loaded last") and by framing path as the creation target. It adds intent beyond the field-level text without duplicating it.

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 ("Creates an empty .vmf") and anchors it to a familiar UI action (Hammer's File > New). It also distinguishes this tool from write_vmf_solid by explaining that sibling reads its target and refuses a file with no `world` block, so the agent can tell the two apart without opening either 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?

It states the condition that selects this tool ("the map every other writer here assumes already exists") and explicitly names a when-not case (it REFUSES to overwrite an existing map). That routing information is exactly what an agent needs to choose between this and the other write_vmf_* tools.

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