read_vmf_leak
Detect whether a .vmf map is sealed without compiling: flood open space from spawn points and report leak paths like a .lin pointfile, so geometry can be fixed before running vbsp.
Instructions
Whether a .vmf is sealed, WITHOUT compiling it. Today the only thing that can answer is vbsp, which costs a toolchain and minutes, and which refuses to run vvis afterwards. This floods the open space from a point inside -- a spawn entity, by default -- and reports where the flood got out, with the path to follow, the same shape as the .lin pointfile. A wall thinner than the cell size is not resolved, so this can miss a leak; it does not invent one, because a cell counts as free only when its whole interior is.
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>"
},
"name": "read_vmf_leak"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Path to the .vmf, absolute or relative to the repo root. | |
| step | No | Cell size in units. 16 is the coarsest that resolves a 32-unit doorway. Halving it multiplies the cell count by eight. | |
| seeds | No | Points known to be inside. Default: every spawn entity in the map. | |
| maxCells | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | ||
| step | Yes | ||
| cells | Yes | ||
| notes | Yes | ||
| seeds | Yes | ||
| sealed | Yes | ||
| leakPath | Yes | ||
| escapedAt | Yes | ||
| openCellCount | Yes | ||
| openVolumeUnits | Yes |