Skip to main content
Glama

move_vertices

Move named brush corners in a VMF to shape convex geometry, rejecting any move that would leave a face non-planar, matching Hammer's vertex editor.

Instructions

Moves named corners of one brush: Hammer's vertex manipulation tool. The last thing between an assembly of cut boxes and an arbitrary convex shape -- it is what pulls a wall out to meet a street that does not run square. Corners are named by position, as read_vmf_solids reports them. It refuses far more than it accepts, and that is parity with the editor rather than a shortfall: moving one corner moves it on every face that shares it, three of them on a box, so a diagonal pull leaves each of those faces with a point off its own plane. Hammer shows that as a red invalid solid and will not build it either. Moves that work are the ones keeping every face flat: a whole edge, or a whole face. Texture axes are left alone, as Hammer leaves them.

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>",
      "solidId": "<solidId>",
      "moves": "<moves>"
    },
    "name": "move_vertices"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath to the .vmf, absolute or relative to the repo root.
movesYesCorners to move, each named by where it is now.
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.
solidIdYesHammer id of the brush. read_vmf_solids lists the corners.
toleranceNoHow close a coordinate must be to a real corner to name it. Default 0.5, because corners read back through JSON are rounded and exact equality would make the tool unusable from outside.

Output Schema

NameRequiredDescriptionDefault
pathYes
movedYes
solidIdYes
writtenYes
nextStepYes
warningsYes
maxsAfterYes
minsAfterYes
unchangedYes
backupPathYes
volumeAfterYes
volumeBeforeYes
planarityErrorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.24-alpha

TDQS

A4/5.0
Behavior4/5

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

Annotations supply only a title, so the description carries the full burden and does so well: it discloses the high rejection rate, explains the geometric reason, notes the red-invalid-solid parity with the editor, and states texture axes are left untouched. It adds nothing about the write itself (backup/confirm behavior lives only in the schema), which keeps it from a 5.

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?

The purpose is front-loaded and the failure-mode discussion earns its place, but the opening image about an assembly of cut boxes and a street that does not run square is roughly forty words of flavor carrying no operational information. Trimming that would make the definition sharper without losing any guidance.

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 mutating, failure-prone tool with no behavioral annotations, the description covers the critical unknown — which moves are legal and why — and an output schema exists so return values need no explanation. Remaining gaps (write/backup semantics) are already documented in the schema.

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 100%, including tolerance, dryRun, backup and the from/to move pairs, so the schema does the heavy lifting. The description reinforces that corners are named 'by position, as read_vmf_solids reports them', but the solidId schema entry already says the same thing, so little meaning is added 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 ('Moves named corners of one brush') and immediately frames it as Hammer's vertex manipulation tool, which distinguishes it from siblings like align_faces or clip_solids that also reshape geometry.

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 unusually explicit when-not guidance: diagonal pulls move a shared corner on three faces and leave each off-plane, so only whole-edge or whole-face moves succeed. It also points to read_vmf_solids for how corners are named. It stops short of routing the agent to an alternative tool when a diagonal move is the goal, so 4 rather than 5.

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