Skip to main content
Glama

transform_solids

Move, rotate, scale, or mirror existing .vmf brushes by ID, owner, material, or bounding box while preserving texture alignment and verifying geometry before writing.

Instructions

Moves, turns, scales or mirrors brushes that are already in a .vmf. Until this existed the write path could only add: a brush placed an inch out of position could not be nudged, only rewritten. Selects by id, owner, material or bounding box, and edits only the plane and texture-axis lines of the brushes it moved -- nothing else in the file shifts by a byte. Texture lock is on by default, so a texture stays where it sits on its face, as in Hammer. The result is read back through read_vmf_solids before the file is touched and the write is refused if any brush stopped being one; volume is reported before and after, and a transform must scale it by its own determinant or something is wrong.

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": "transform_solids"
  }
}

Input Schema

NameRequiredDescriptionDefault
gridNoRound every corner to this grid afterwards. Default 0, which rounds nothing. Snapping is what makes a face stop being flat, so what it costs is measured and reported as planarityError rather than assumed to be nothing.
moveNoTranslate by this, in Hammer units.
pathYesPath to the .vmf, absolute or relative to the repo root.
ownerNo'world', or a brush entity classname such as func_detail.
scaleNo
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.
mirrorNo
rotateNoMultiples of 90 are exact; other angles leave the brush off the grid, as Hammer does.
withinNoBrushes lying entirely inside this box. Entirely, not partly: a half-caught brush is how a box selection catches something the caller could not see it had touched.
confirmNoRequired (true) to run this tool: it writes or executes.
materialNoBrushes carrying this on at least one face. Substring, case-insensitive.
solidIdsNoHammer ids, as read_vmf_solids reports them.
textureLockNoDefault true: the texture stays put on its face. Refused on a scale that stretches one axis more than another, because no texture axis pair can express that -- pass false to accept the stretch.

Output Schema

NameRequiredDescriptionDefault
pathYes
solidsYes
matchedYes
writtenYes
nextStepYes
warningsYes
unchangedYes
backupPathYes
planarityErrorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.24-alpha

TDQS

A4.1/5.0
Behavior5/5

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

Annotations carry nothing beyond a title, so the description does the full job and does it well: only plane and texture-axis lines change, backup defaults on, dryRun runs every verification, texture lock defaults on and is refused on non-uniform scaling, the result is re-read through read_vmf_solids and refused if a brush became degenerate, and volume is checked against the scale determinant. This is exactly the mutation-safety 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?

Front-loaded with the core action, followed by scope, selection, and safety guarantees in a logical order. Some phrasing is colorful ('nothing else in the file shifts by a byte', the historical aside) but each sentence still carries substantive information.

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 14-parameter mutation tool with nested rotate/scale/mirror/within objects and an output schema, the description covers file-safety, verification and selection adequately. The main gap is composition semantics — whether multiple transform parameters may be supplied together and how they are ordered — plus no mention of the required confirm flag.

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 description coverage is 86%, so the parameters largely document themselves, and much of what the prose says about textureLock, pivot defaults and grid snapping is already in the schema. The description adds little parameter-level meaning beyond those fields — notably it never explains how move/rotate/scale/mirror combine or in what order they apply.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a precise verb set (moves, turns, scales, mirrors) and a precise resource (brushes already in a .vmf), and contrasts itself with the add-only write path. It never explicitly contrasts with the vertex-level sibling (move_vertices) or edit_vmf, so sibling differentiation is incomplete for a 5.

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 a concrete motivating scenario — nudge a brush placed an inch out of position rather than rewriting it — and describes how the selection is made (id, owner, material, bounding box). It offers no explicit 'use X instead' routing to move_vertices, clip_solids or edit_vmf, and states no when-not-to-use conditions.

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