Skip to main content
Glama

read_vmf_sightlines

Find the longest clear lines of sight in an uncompiled .vmf by sampling standable cells, so mappers can judge sight-line length before running a compile.

Instructions

The longest clear lines of sight in an UNCOMPILED .vmf, sampled from the places a person can actually stand. read_sightlines answers the same question on a compiled map by sampling ground in a column, which picks up roofs and the spawn room under the map; this samples the standable cells the room pass found, which is a stronger constraint and needs no vbsp. Long sight lines are what a mapper trades away for framerate, so the number is a design decision rather than a fault.

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

Input Schema

NameRequiredDescriptionDefault
pathYes
stepNo
limitNo
seedsNo
spacingNoTake one sample cell in this many, per axis. Pairs cost the square of this.
maxCellsNo
eyeHeightNo

Output Schema

NameRequiredDescriptionDefault
pathYes
notesYes
longestYes
pairsTestedYes
samplePointsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.24-alpha

TDQS

A3.7/5.0
Behavior3/5

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

With no readOnlyHint/destructiveHint annotations, the description carries the burden; it implies a read operation and discloses the sampling basis (standable cells from the room pass) and the no-compile requirement. It leaves open whether the room pass must be run beforehand or whether this tool triggers it internally, and says nothing about cost beyond the rationale.

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?

Front-loaded with the capability, then the sibling contrast, then rationale; sentences are dense and purposeful. The closing observation that long sight lines are a design decision is interpretive rather than operational, a minor amount of non-essential text.

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

Completeness3/5

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

Purpose and sibling routing are fully covered and an output schema exists, so return values need no explanation. For a 7-parameter tool with 14% schema coverage, though, the description never addresses the six undocumented parameters, which is a genuine gap for correct invocation.

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

Parameters2/5

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

Seven parameters with only 14% schema description coverage, and the description mentions no parameter names, units, or defaults. 'Sampled from the places a person can actually stand' loosely gestures at seeds/step/eyeHeight but adds no usable meaning, so the low-coverage schema is not compensated.

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

Purpose5/5

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

Names a specific verb+resource ('longest clear lines of sight') plus a precise scope ('in an UNCOMPILED .vmf, sampled from places a person can actually stand'). It explicitly separates itself from read_sightlines, so an agent can pick between them without opening either schema.

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

Usage Guidelines4/5

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

Gives a clear selection rule: use this for an uncompiled .vmf, use read_sightlines for a compiled map, and notes this route 'needs no vbsp'. That is explicit when-to-use guidance with a named alternative; there is no explicit when-not-to-use beyond that contrast, and no prerequisite statement about the room pass.

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