Skip to main content
Glama

hollow_solids

Hollows solid VMF brushes into room walls with mitred corners, preserves face materials, and verifies exact wall volume before writing to prevent invalid geometry.

Instructions

Turns solid blocks into the walls of a room. Hammer has this and Hammer's version overlaps at the corners: each wall spans its whole face, so two adjacent walls both occupy the corner between them. This one mitres, because 'this point is nearer face i than face j' turns out to be a plane, so each wall stays a single convex brush and no two share a cubic unit. The check is exact: the walls must sum to the outer volume less the room inside, and the tool refuses to write if they do not. Each wall keeps the material the source brush had on that face; the inner surface and the mitres take innerMaterial, which defaults to nodraw so a hollowed block does not become a room with brick on the outside of its own walls.

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>",
      "thickness": "<thickness>"
    },
    "name": "hollow_solids"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath to the .vmf, absolute or relative to the repo root.
ownerNo'world', or a brush entity classname.
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.
withinNo
confirmNoRequired (true) to run this tool: it writes or executes.
materialNoBrushes carrying this on at least one face.
solidIdsNoHammer ids of the brushes to hollow.
directionNo'in' keeps the outer surface where it was; 'out' keeps the inner one.in
thicknessYesWall thickness, in Hammer units.
keepSourceNoLeave the original brush in place. Default false, because a block left inside its own walls is still a solid block.
innerMaterialNoMaterial for the faces hollowing created. Default TOOLS/TOOLSNODRAW.

Output Schema

NameRequiredDescriptionDefault
pathYes
matchedYes
writtenYes
hollowedYes
nextStepYes
warningsYes
unchangedYes
backupPathYes
solidsAfterYes
solidsBeforeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.24-alpha

TDQS

A3.7/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 disclosure burden and does well: it states the volume-sum verification is exact and that 'the tool refuses to write if they do not,' which is a real guardrail an agent must anticipate. It also explains material preservation per face and why innerMaterial defaults to nodraw. It does not mention the file-write/confirm/backup prerequisites, though those are covered by the schema's parameter descriptions.

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?

Purpose is front-loaded in sentence one, and the rest is dense but mostly on-topic. The derivation of why the mitre is a plane ('this point is nearer face i than face j') is engineering rationale rather than invocation guidance, but it directly supports the claim that walls are single convex brushes and never share a cubic unit, which the agent does need to know.

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?

This is a twelve-parameter mutation tool with a nested object and an output schema, so the description only needs to cover operation semantics — which it does, including the write gate, material rules, and output geometry. Backup, confirm, dryRun and scope parameters are handled by rich schema descriptions, so no critical gap remains, though a one-line note that the tool writes to disk by default would round it out.

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?

With 92% schema description coverage, the schema already documents nearly every parameter, so the baseline is 3. The description does add genuine meaning for innerMaterial — that it applies to the inner surface and the mitres, and why nodraw is the default — plus the rule that each wall inherits the source brush's face material. That is useful but confined to one or two of the twelve parameters.

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?

The first sentence gives a concrete verb and resource: 'Turns solid blocks into the walls of a room.' It also draws a sharp contrast with Hammer's own hollowing by explaining the mitring geometry, so an agent knows exactly what operation this performs. It stops short of naming the other MCP solids tools (clip_solids, delete_solids) as alternatives, so sibling differentiation is implicit rather than stated.

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?

Usage is only implied through the geometry narrative: reach for this when you want a block converted to a room with non-overlapping walls. There is no explicit 'use this when X, not when Y' statement and no routing to clip_solids or delete_solids for adjacent operations. The comparison to Hammer's version is the only contrast offered, and that is not a sibling tool.

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