read_map_report
Judges a compiled .bsp against a budget profile and returns pass, warn, fail, or skipped verdicts per criterion, so agents know whether map limits are acceptable.
Instructions
Judges a compiled map against a budget profile and returns a verdict per criterion, not just numbers. This is the tool that gives an agent a stopping condition: every other reader here answers 'how much', this one answers 'is that enough'. Covers lump fill against vbsp's ceilings, entity count against the edict budget, LIGHTING against MAX_MAP_LIGHTING, whether vvis ran at all, how finely the world is split, and whether cubemaps and HDR exist. Limits come from Valve's headers; thresholds come from the profile and each one states its own provenance, including when it was simply chosen. A criterion nothing calibrates reports 'skipped' with the reason rather than a confident verdict about nothing.
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_map_report"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Path to the .bsp, absolute or relative to the repo root. | |
| profile | No | Budget profile id. 'source-stock' (default) asks only whether the map will compile and load, using stock Source 2013 ceilings. No L4D2-specific budget has been calibrated yet. | |
| verdicts | No | Return only these verdicts. Omit for all of them. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | ||
| overall | Yes | ||
| profile | Yes | ||
| summary | Yes | ||
| criteria | Yes | ||
| filteredOut | No |