read_vmf_rooms
Reads a .vmf's geometry to identify rooms, door openings, and connections without compiling or annotations, helping you determine how many rooms exist and what connects to what.
Instructions
The rooms of a .vmf, the openings between them, and how they connect -- from the geometry alone, with no compilation and no annotation in the file. Rooms come from a watershed on the clearance field, NOT from connected components: a sealed map has exactly one of those. This is a heuristic and it says so, with the parameters that produced it; it can split a hall with a pillar in it and swallow an alcove. Widths are voxel estimates to within a cell. Use it to ask what a place IS -- how many rooms, how wide the doors, what connects to what -- rather than what is at a coordinate.
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_rooms"
}
}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 | ||
| mergeLimit | No | How many merges to report, newest first-hit last. mergeCount stays exact. | |
| minRoomArea | No | Below this floor area, in square units, a region is merged into its largest neighbour. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | ||
| notes | Yes | ||
| rooms | Yes | ||
| merges | Yes | ||
| method | Yes | ||
| sealed | Yes | ||
| portals | Yes | ||
| roomCount | Yes | ||
| mergeCount | Yes | ||
| parameters | Yes | ||
| unreachable | Yes |