read_vmf_visibility
Checks whether named pairs of points in an uncompiled .vmf can see each other, reports the brush, face, and material blocking each blocked view, and flags endpoints stuck inside geometry.
Instructions
Whether each of several named pairs of points can see each other in an uncompiled .vmf, and what blocks the ones that cannot -- by brush id, face and material. read_sightlines answers a different question on a compiled map: it samples the ground and finds the LONGEST lines. This one answers about sight lines you name, which is what 'does moving this wall break the view from the lobby to the desk' needs. Also reports the nearest surface to each endpoint, so an endpoint accidentally inside geometry is visible as such rather than reported as blind.
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>",
"pairs": "<pairs>"
},
"name": "read_vmf_visibility"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mask | No | What counts as an obstacle. `sight` sees through clip brushes, `player` does not, `solid` is the world as vbsp builds it. The difference between 'can they see the door' and 'can they reach it'. | solid |
| path | Yes | Path to the .vmf, absolute or relative to the repo root. | |
| pairs | Yes | ||
| owners | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | ||
| clear | Yes | ||
| lines | Yes | ||
| notes | Yes | ||
| blocked | Yes | ||
| excluded | Yes | ||
| brushCount | Yes |