read_leak
Reads a .lin leak pointfile beside a .vmf or .bsp and names the entities nearest the path start, revealing which entity sees the void. Returns leaked:false when no pointfile exists.
Instructions
Turns a leak into a location. vbsp says only 'leaked!' and writes a .lin pointfile beside the map: this reads it and names the entities nearest to where the path starts, which is the entity that can see the void. Pass the .lin, or the .vmf or .bsp beside it. Both ends of the path are correlated, because vbsp does not guarantee which end holds the entity -- on a two-point pointfile it was the last. No pointfile is an ANSWER, not an error: it returns leaked:false, and compiled tells a map that did not leak from one nothing has compiled here. A .bsp that arrived from somewhere else -- a Workshop .gma, a copy, a download -- carries no .lin and never could, so establishedBy says whether the answer rests on evidence or on the absence of a file that was never going to be there.
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_leak"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | The .lin pointfile, or the .vmf/.bsp it sits beside. | |
| limit | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| end | No | ||
| note | Yes | ||
| start | No | ||
| leaked | Yes | ||
| points | No | ||
| compiled | Yes | ||
| evidence | Yes | ||
| pointfile | Yes | ||
| spanUnits | No | ||
| pointCount | No | ||
| nearestToEnd | No | ||
| establishedBy | Yes | ||
| leakingEntity | No | ||
| nearestToStart | No | ||
| correlatedAgainst | No |