check_vmf_rules
Validates a .vmf against its map-specific .rules.json, reporting rule violations with worst points or skipped rules when no rules file exists.
Instructions
Checks a .vmf against ITS OWN rules file -- <map>.rules.json, a sibling of the .vmf. 'Four metres of pavement, no entrance obstructed, the view from the lobby preserved' is a design brief, and this is the form of it a machine can check. Per map and never global: a residential street and a warehouse have different right answers for every number, and a shared default would be wrong for both while looking authoritative. No rules file means NO checking, not checking against something reasonable. It REPORTS: the writing tools do not consult it and must not, because a mapper may want a narrow alley. Every violation carries the worst point, so render_vmf_view or render_vmf_plan can be pointed straight at it. Read overall, not errorCount: a run in which some rule matched nothing comes back 'skipped', never 'pass'.
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": "check_vmf_rules"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Path to the .vmf, absolute or relative to the repo root. | |
| step | No | ||
| limit | No | ||
| seeds | No | Points inside the map, for rules about rooms. Default: the spawn entities. | |
| maxCells | No | ||
| severity | No | Report only violations at least this severe. | all |
| eyeHeight | No | Height above each end's origin that a sightline is traced at. Source's own eye is 64. It is in every sightline violation's message, because a rule that fails on a lintel is otherwise indistinguishable from one that fails on a wall. | |
| rulesPath | No | Override the sibling file. There is no search up the directory tree. | |
| minRoomArea | No | Below this floor area, in square units, a region is merged into its largest neighbour. The same knob read_vmf_rooms takes: pass both the same value, or a diagnosis and the verdict it explains are about different segmentations. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | ||
| notes | Yes | ||
| overall | Yes | ||
| reported | Yes | ||
| rulesPath | Yes | ||
| errorCount | Yes | ||
| rulesFound | Yes | ||
| violations | Yes | ||
| rulesChecked | Yes | ||
| segmentation | Yes | ||
| warningCount | Yes | ||
| matchedNothing | Yes |