Skip to main content
Glama

set_smoothing_groups

Assign Hammer smoothing groups (1–32) to selected VMF faces so shared edges light as continuous surfaces; converts group numbers to bitmasks and can clear groups.

Instructions

Sets the smoothing groups on selected faces. Two faces sharing an edge and a group are lit by vrad as one continuous surface; without it every facet of a curve is lit separately and reads as the flat polygons it really is. Takes Hammer's own group numbers, 1 to 32, and does the bit shifting -- the file stores a bitmask, so group 13 is 4096 and getting that wrong is silent. Pass an empty list to clear 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>",
      "groups": "<groups>"
    },
    "name": "set_smoothing_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNoEvery face of the map. Required when no other criterion is given.
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.
facingNoOnly faces pointing this way. 'up' is a floor, 'down' a ceiling, 'side' a wall; the cut is at 45 degrees, so a ramp counts as what it is closer to being.
groupsYesHammer's group numbers, 1 to 32. Empty clears every group.
confirmNoRequired (true) to run this tool: it writes or executes.
minAreaNoOnly faces at least this large, in square units.
materialNoOnly faces already carrying this. Substring, case-insensitive.
solidIdsNoOnly faces of these solids.

Output Schema

NameRequiredDescriptionDefault
maskYes
pathYes
matchedYes
writtenYes
nextStepYes
warningsYes
unchangedYes
backupPathYes
facesChangedYes

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?

With no meaningful annotations beyond a title, the description carries the disclosure burden and does well: it warns that the file stores a bitmask, that the tool handles shifting, and that a wrong value fails silently. It does not explicitly state that the tool writes to disk or requires confirmation, though the schema covers those details.

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

Conciseness5/5

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

The definition is three tight sentences and front-loads the purpose. Each sentence adds useful information: the effect, the bitmask risk, and the clearing behavior; there is no filler.

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 mutation tool with full schema coverage and an output schema, the description gives the essential domain behavior and the most dangerous implementation detail. It leaves selection-filter semantics and write/backup/confirmation behavior to the schema, which is acceptable but means it is not fully exhaustive.

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 description coverage is 100%, so the baseline is 3. The description adds meaningful semantic detail for the key groups parameter, including Hammer's number range, the bitmask storage model, the group 13 = 4096 example, and the empty-list clearing behavior.

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?

The first sentence states a specific verb and resource: sets smoothing groups on selected faces. It explains the visual/lighting effect, which makes clear what the operation accomplishes, and it is distinguishable from sibling setters like set_face_material or set_lightmap_scale.

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 explains why smoothing groups matter and notes that an empty list clears them, implying when to use the tool. However, it gives no explicit when-not guidance and does not name or compare against any alternative tool.

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