Skip to main content
Glama

set_cordon

Set the cordon box and toggle it on or off to control which parts of a VMF compile. Use it to test one room quickly or confirm whether a cordon is active.

Instructions

Sets the cordon box and whether it is on. The only piece of a map's organisation that changes what compiles: with the cordon on, vbsp is handed only what the box contains and everything outside it is simply not in the map. It is how a mapper tests one room of a city without waiting for the city, and it is also how a map ships with three quarters of itself missing -- vbsp does not warn, because from its point of view nothing is wrong. Setting it always reports whether it is active.

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>",
      "mins": "<mins>",
      "maxs": "<maxs>"
    },
    "name": "set_cordon"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxsYes
minsYes
nameNoDefault 'cordon'.
pathYesPath to the .vmf, absolute or relative to the repo root.
activeNoDefault true. False leaves the box and turns it off.
backupNoCopy the file to <file>.bak before writing. Nothing is copied on a no-op.
dryRunNoCheck and report without writing. Every verification runs either way.
confirmNoRequired (true) to run this tool: it writes or executes.

Output Schema

NameRequiredDescriptionDefault
nameYes
pathYes
activeYes
writtenYes
nextStepYes
warningsYes
unchangedYes
backupPathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.24-alpha

TDQS

A4.3/5.0
Behavior5/5

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

Annotations carry only a title, so the description bears the full burden and delivers: it explains that vbsp receives only the box contents, that everything outside is silently excluded, that vbsp emits no warning, and that the call reports whether the cordon is active. This is exactly the non-obvious behavioral context an agent needs before a destructive-ish write.

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 core action, then the compile-impact explanation and the silent-failure warning. The narrative about testing one room earns its place as a usage cue, though the sentence is long and could be tightened.

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 covers the critical behavioral risk (silent exclusion of geometry). It is complete for correct invocation, with only minor gaps around the non-core parameters that the schema already documents.

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 coverage is 75% and the schema already documents path, name, active, backup, dryRun, and confirm. The description only implicitly touches the 'active' parameter ('whether it is on') and adds no meaning for mins/maxs, backup, dryRun, or confirm. Baseline 3 is appropriate since the schema does the heavy lifting.

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?

States a specific verb and resource ('Sets the cordon box and whether it is on') and immediately distinguishes this tool from other map-organisation settings by noting it is 'the only piece of a map's organisation that changes what compiles.' An agent can tell exactly what this does and how it differs from siblings like set_visgroup or set_map_properties.

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 concrete when-to-use context ('how a mapper tests one room of a city without waiting for the city') and a strong when-to-be-careful warning about shipping with the cordon on. It does not name an alternative tool for the shipping scenario, but the usage conditions are clear and actionable.

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