Skip to main content
Glama

set_solid_class

Moves brushes into or out of func_detail to keep trim, pillars and window frames from splitting the BSP tree, cutting compile time and improving the PVS. It does not seal the map.

Instructions

Moves brushes between the world and a brush entity -- in practice, into or out of func_detail. This is the largest single lever on a Source map's performance and it is invisible in a compiled .bsp, because vbsp folds func_detail into the world: a shipped map cannot tell you which brushes were structural. A structural brush splits the BSP tree and spawns visleaves, so trim, pillars and window frames cost a slower compile and a worse PVS for nothing. WARNING: a func_detail brush does not seal the map. Move a wall into one and the next compile leaks, and no check here can rule that out -- sealing is a property of the whole hull. Compile afterwards and read the leak.

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>",
      "solidIds": "<solidIds>",
      "to": "<to>"
    },
    "name": "set_solid_class"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes'world' to make them structural again, or a brush entity classname such as func_detail, func_illusionary, func_brush.
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.
confirmNoRequired (true) to run this tool: it writes or executes.
entityIdNoExisting entity of that class to add to. Omit to create one. Grouping is taste, not performance: vbsp dissolves every func_detail into the world regardless.
solidIdsYesHammer ids of the solids to move. read_vmf_solids lists them.

Output Schema

NameRequiredDescriptionDefault
pathYes
movedYes
writtenYes
nextStepYes
warningsYes
unchangedYes
backupPathYes
createdEntityIdYes
worldSolidsAfterYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.24-alpha

TDQS

A4/5.0
Behavior3/5

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

Annotations only carry a title, so the description bears the full disclosure burden. It does well on the central risk -- func_detail brushes don't seal, a moved wall will leak, and no check here can rule that out -- plus explicit instruction to compile and read the leak afterwards. It says nothing about write safety beyond backup/dryRun living in the schema, and 'invisible in a compiled .bsp' is explanatory color rather than behavior.

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 the first clause and the WARNING is clearly flagged. The BSP-visleaf sentence earns its place by justifying the tool, but it is the sort of detail that could be trimmed without losing the call decision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and the schema documents all seven parameters, so the description need not cover returns or arguments. What remains missing is the write/confirm contract and what a leak-free result looks like procedurally, though the sealing warning covers the largest correctness risk for a moderately complex mutation tool.

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 prose adds a little: it frames the choice as a binary structural/detail decision and reinforces that solidIds come from read_vmf_solids, and it pre-empts the entityId grouping question by noting vbsp dissolves all func_detail regardless.

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 concrete verb and resource ('Moves brushes between the world and a brush entity') and immediately narrows the real-world case to func_detail. An agent can distinguish this from structural-edit siblings like group_solids or write_vmf_solid purely from the wording.

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 clear criterion for when to use it: trim, pillars and window frames that don't seal the map should be non-structural. It also points to read_vmf_solids for obtaining ids. It never names a sibling to use instead for the opposite direction, but the guidance is otherwise unambiguous.

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