Skip to main content
Glama

clip_solids

Cuts VMF brushes with a plane, keeping the front, back, or both halves while preserving surviving face materials, texture axes, lightmap scale, and smoothing groups.

Instructions

Cuts brushes with a plane, keeping the front, the back, or both. This is Hammer's clip tool, the most-used one in the editor and the one that unlocks every shape that is not an assembly of boxes. A face that survives keeps its own material, texture axes, lightmap scale and smoothing groups -- the side block is copied, not rebuilt. A face that no longer bounds anything is dropped rather than left redundant. The new face gets its axes from vbsp's base-axis table and inherits the material of the largest face kept, which is what Hammer does. Keeping both halves is the check: their volumes must sum to the original, and the tool refuses to write if they do not.

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>",
      "plane": "<plane>",
      "keep": "<keep>"
    },
    "name": "clip_solids"
  }
}

Input Schema

NameRequiredDescriptionDefault
keepYes'front' is the side the normal points towards. 'both' leaves two brushes.
pathYesPath to the .vmf, absolute or relative to the repo root.
ownerNo'world', or a brush entity classname.
planeYesThe cutting plane, as a point and a normal or as three points.
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.
withinNoBrushes lying entirely inside this box.
confirmNoRequired (true) to run this tool: it writes or executes.
materialNoBrushes carrying this on at least one face.
solidIdsNoHammer ids of the brushes to cut.
cutMaterialNoMaterial for the new face. Default: the material of the largest face kept.

Output Schema

NameRequiredDescriptionDefault
pathYes
solidsYes
matchedYes
writtenYes
nextStepYes
warningsYes
unchangedYes
backupPathYes
solidsAfterYes
solidsBeforeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.24-alpha

TDQS

A4.1/5.0
Behavior4/5

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

With only a title annotation, the description carries the burden and does well: it discloses that surviving faces keep material, texture axes, lightmap scale and smoothing groups, that the side block is copied rather than rebuilt, that non-bounding faces are dropped, how the new face's axes and material are derived, and that it refuses to write when the two halves' volumes do not sum. It omits write-safety behavior such as backup, dryRun and the confirm gate, leaving those to the schema.

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?

Five sentences, front-loaded with the core action and result, then behavior, then verification. Dense and mostly waste-free, though 'which is what Hammer does' and the repeated editor-praise clause are 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?

For an 11-parameter destructive mutation with no meaningful annotations, the description covers geometry semantics, face preservation, and a self-check, and an output schema exists so return values need not be described. It stops short of addressing file-write safety and brush-selection behavior, but nothing critical to calling it correctly 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 baseline is 3; the description still adds meaning by explaining what 'front' means geometrically for the keep parameter and by describing the cutMaterial default (largest face kept) and why the new face's orientation comes from vbsp's base-axis table. It says nothing about the selection parameters (solidIds, within, material, owner), which are covered only by 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?

Opens with a specific verb and resource plus scope: 'Cuts brushes with a plane, keeping the front, the back, or both.' The 'Hammer's clip tool' framing and the note about unlocking non-box shapes separate it clearly from hollow_solids, delete_solids and transform_solids without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description conveys when this is the natural tool ('the one that unlocks every shape that is not an assembly of boxes'), which is implied guidance rather than explicit. It never names an alternative sibling or states when not to use it, nor does it mention prerequisites such as selecting brushes via solidIds/within before clipping.

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