Skip to main content
Glama

read_prop_survey

Inventory a compiled map's prop entities by model and class, and flag prop_dynamic entities with no name, parent, animation or outputs — candidates to convert to prop_static and cut server entity count.

Instructions

Inventory of a compiled map's prop entities, by model and by class, plus the prop_dynamic entities that carry no name, no parent, no animation and no output. Those are dynamic for no reason: each is a real server entity that ticks and is counted by anything walking ents.GetAll(), where a prop_static costs nothing. The list is a starting point, not a verdict -- converting needs a recompile, and a model without static support cannot be converted at all.

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_prop_survey"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath to the .bsp, absolute or relative to the repo root.
limitNoCap on the listed conversion candidates.

Output Schema

NameRequiredDescriptionDefault
pathYes
byClassYes
byModelYes
propTotalYes
totalEntitiesYes
staticCandidatesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.24-alpha

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations carry only a title, so the description bears the burden of disclosure. It adds real behavioral context: the listed prop_dynamic entities are live server entities that tick and are counted by ents.GetAll(), while prop_static costs nothing. It doesn't state that this is a read-only operation or describe result shape/pagination, though the presence of an output schema covers return values.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core inventory statement and the candidate list are front-loaded, and the caveats are useful. Some editorializing ('Those are dynamic for no reason') and partial restatement of the unnamed/unparented criteria slightly inflate length without adding selection value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with an output schema, this covers purpose, the nature of what's flagged, and the key limitation that a static-supporting model is required before conversion. Nothing essential for correct invocation is missing, though the relationship to entity-dump siblings is only implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both path and limit (including its default and 1-2000 bounds) are already fully documented in the schema. The description adds no parameter-level meaning, which is the correct baseline when the schema does the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb+resource framing: an inventory of a compiled map's prop entities, grouped by model and class, plus unnamed/unparented prop_dynamic entities. That scope is distinct from a general entity dump like read_bsp_entities, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied (surveying props as conversion candidates to prop_static) rather than stated as when-to-use. The closing caveats -- conversion requires a recompile, models without static support can't convert -- guide interpretation of results, but the description never names an alternative tool or an exclusion condition for calling this one.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.