Skip to main content
Glama

write_vmf_fitting

Build door casings, counters, skirting and cornices as articulated multi-brush assemblies from a mins/maxs envelope, preventing flat single-slab fittings.

Instructions

Builds the things a room is finished with -- a door casing, a counter, skirting or a cornice -- as the several brushes each of them actually is. write_vmf_solid makes one convex shape per call, so an agent that thinks 'counter' writes a box: three rounds of building maps with these tools produced counters, shelving and doorways that were each a single slab, with a door texture painted flat on a wall where a frame should be. The trade here is that you own the envelope and this owns the articulation -- give it the same mins/maxs you would have given a box and get a worktop with a nosing over a body over a recessed kick. Every internal dimension comes from a table measured off models Valve ships (read_model_info, 13/08/2026), which also found that Source's world is built a third taller than its own player: a door leaf is 108 units, a shop counter 56, with the eye at 64. Refuses any assembly whose parts share an interior or fail to join up, which is a class of error per-brush validation cannot see.

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>",
      "fittings": "<fittings>"
    },
    "name": "write_vmf_fitting"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath to the .vmf, absolute or relative to the repo root.
backupNoCopy the file to <file>.bak before writing. Nothing is copied on a no-op.
dryRunNoCheck and report without writing. Every verification runs either way.
confirmNoRequired (true) to run this tool: it writes or executes.
entityIdNoHammer id of a brush entity to add them to. Omit to add them to the world.
fittingsYesWhat to build, in order.
materialNoMaterial for every face. Default TOOLS/TOOLSNODRAW.
materialsNoMaterial per role, as write_vmf_solid takes it and at the same threshold.
textureScaleNoTexture scale on both axes. Default 0.25.
lightmapScaleNoLuxels per unit on every face. Default 16.

Output Schema

NameRequiredDescriptionDefault
pathYes
builtYes
notesYes
targetYes
writtenYes
solidIdsYes
verifiedYes
warningsYes
backupPathYes
bytesAddedYes
solidsAfterYes
solidsBeforeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.24-alpha

TDQS

A4.2/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 load and does well: it discloses the validation/refusal behavior (assemblies whose parts share an interior or fail to join are rejected, an error class per-brush validation cannot see) and explains that dimensions come from a measured table. It does not say whether existing brushes at that location are replaced or coexisting, leaving one behavioral gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first clause, but the middle is anecdotal: three rounds of building maps, past single-slab counters, and a dated model-measurement note that reads as justification rather than instruction. Shorter would be sharper, though nothing is actively misleading.

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 10-parameter tool with nested union variants and an output schema, the description covers what it builds, how envelopes map to parts, and the refusal behavior. Return shape is covered by the output schema and file/entity routing by the input schema, so remaining gaps are minor.

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 baseline is 3, and the description earns above that by explaining the envelope-versus-articulation contract for mins/maxs: hand it a box-sized envelope and get a worktop with a nosing over a body over a recessed kick. That adds meaning the schema's 'low corner'/'high corner' text does not convey.

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 set: builds door casings, counters, skirting and cornices 'as the several brushes each of them actually is'. It explicitly contrasts with write_vmf_solid producing one convex shape per call, so an agent can pick the right tool 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit routing rule against the main sibling: write_vmf_solid when you want a single convex box, this tool when you want articulation within an envelope. Also tells the agent to supply the same mins/maxs it would have given a box. No explicit when-not beyond the refusal conditions, so not a 5.

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