Skip to main content
Glama

measure_vmf_approach

Measure clear space in front of VMF entities like doors and buttons to catch geometry blocked by walls or crates before compiling.

Instructions

How much clear room a person has in front of the entities of a .vmf -- doors, buttons, vending machines, anything with an origin and a yaw. The classic fault it finds is a door that opens into a wall, or a button behind a crate, neither of which any compiler mentions. It does NOT say whether a door can swing: a leaf's width lives in a model this server cannot open offline, and the hull it assumed is reported rather than quietly folded into the answer.

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": "measure_vmf_approach"
  }
}

Input Schema

NameRequiredDescriptionDefault
hullNoSource's own player hulls: 32x32x72 standing, 32x32x36 crouching.standing
pathYes
limitNo
classnameNoOnly entities whose classname contains this.
targetnameNo
minClearUnitsNoReport only entities with less than this in front. 0 reports all of them.

Output Schema

NameRequiredDescriptionDefault
pathYes
notesYes
matchedYes
entitiesYes
reportedYes
assumedHullYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.24-alpha

TDQS

A3.5/5.0
Behavior4/5

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

The annotations are essentially empty (title only), so the description carries the full burden and does so well: it discloses an important limitation (it cannot judge whether a door can swing, since leaf width lives in a model the server cannot open offline) and states that the assumed hull is reported rather than silently baked into the result. That negative-space disclosure is exactly the kind of behavior an agent needs. It loses a point for not covering cost, error behavior on bad paths, or the meaning of the reported hull value.

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?

Three sentences, each carrying real information: purpose, the faults it finds, and the swing caveat. The first sentence is a fragment that starts with "How much..." which reads slightly awkwardly but is front-loaded with the core idea. Little waste overall.

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?

An output schema exists, so return values need not be explained, and the description appropriately focuses on intent and limitations. The gap is parameter-level: for a six-parameter tool with only 50% schema coverage, the description should say something about classname/targetname filtering or the minClearUnits threshold, since those shape the answer.

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?

Schema description coverage is 50%, with path, targetname, and limit undocumented in the schema. The description adds no parameter guidance at all — it never mentions path, classname, targetname, limit, or minClearUnits — and only glancingly references hull by saying the assumed hull is reported. It therefore fails to compensate for the coverage gap.

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 measurement framing ("How much clear room a person has in front of the entities") and enumerates the target objects (doors, buttons, vending machines, anything with origin and yaw). That is a concrete verb+resource. It falls short of a 5 because it never distinguishes itself from the sibling measure_vmf_clearance, so an agent cannot tell the two measurements apart from the text alone.

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?

It gives a useful motivating context — the classic faults it catches are doors opening into walls and buttons behind crates that compilers ignore — which implies when to reach for it. However, it never states explicit when/when-not conditions or names an alternative tool to use instead, so the agent must infer that this is the pre-fab-detailing proximity check rather than a general clearance check.

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