read_entity_report
Lists every entity and its keyvalues from a .vmf or .bsp, filtered by classname, targetname, or key presence, so mappers can find specific entities such as doors with spawnflags 512.
Instructions
Hammer's Entity Report: every entity with its keyvalues, filterable by classname, targetname or the presence of a key. Takes a .vmf or a compiled .bsp -- on a map with no source this is not a convenience, it is the only way to ask. read_vmf counts entities by classname and read_bsp_entities gives a histogram; neither answers 'which entity has spawnflags 512', which is the question the report exists for and how a mapper finds the one door of forty that was left locked. A compiled entity has no Hammer id and owns no solids inline, so id is null and solidCount is 0 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_entity_report"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Path to the .vmf or .bsp, absolute or relative to the repo root. | |
| limit | No | ||
| hasKey | No | Only entities carrying this keyvalue. | |
| keyValue | No | With hasKey: the exact value it must have. | |
| classname | No | Substring, case-insensitive. | |
| targetname | No | Substring, case-insensitive. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | ||
| format | Yes | ||
| matched | Yes | ||
| entities | Yes | ||
| returned | Yes | ||
| byClassname | Yes |