Skip to main content
Glama

set_map_properties

Set worldspawn keyvalues like skyname, detail sprite/material pairs and prop fade width in a VMF, keeping paired detail values consistent so map grass renders with sprites and material.

Instructions

Sets the keyvalues that really live on worldspawn: the sky, the detail sprites, the prop fade width. Ordinary keyvalues on an ordinary entity, so this is edit_vmf with a shorter name -- except that detailvbsp and detailmaterial come as a pair, and setting one without the other gives a map whose grass either has no sprites or has sprites with no material, which vbsp mentions neither of. Fog is NOT here: Source reads fogenable, fogstart, fogend and fogcolor from an env_fog_controller, and writing them to worldspawn gives a file that parses and no fog in game. Create the controller with edit_vmf.

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

Input Schema

NameRequiredDescriptionDefault
pathYesPath to the .vmf, absolute or relative to the repo root.
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.
skynameNo
detailvbspNoWhich sprites go on which material.
detailmaterialNoThe sprite sheet itself.
maxpropscreenwidthNo

Output Schema

NameRequiredDescriptionDefault
pathYes
changedYes
writtenYes
nextStepYes
warningsYes
unchangedYes
backupPathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.24-alpha

TDQS

A4.1/5.0
Behavior4/5

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

With no readOnly/destructive annotations, the description carries the burden and largely meets it: it warns that detailvbsp and detailmaterial must be set as a pair or the map compiles with broken grass, and that writing fog to worldspawn yields a file that parses but shows no fog. It does not say whether existing values are overwritten or that a window may silently ignore these settings.

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 statement and the two critical caveats, with no filler about backup or dryRun already covered by the schema. The aside about vbsp warnings is slightly verbose but earns its place as a failure-mode hint.

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 no explanation, and the write-safety parameters are documented in the schema. Adding only the pairing and fog pitfalls leaves little missing for a write tool of this scope.

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%, so the baseline is a 3. The description adds conceptual meaning by mapping 'sky' and 'prop fade width' to the mostly-undocumented skyname and maxpropscreenwidth params and by explaining the detailvbsp/detailmaterial pairing, but it never names the latter parameters explicitly.

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 and resource (sets keyvalues on worldspawn) and enumerates the concrete keys it covers: sky, detail sprites, prop fade width. It also defines itself against a sibling ('edit_vmf with a shorter name') and rules out fog, so an agent can tell what belongs here.

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 when-not: fog keyvalues must go through an env_fog_controller created with edit_vmf, with the reason stated. The only soft spot is that 'edit_vmf with a shorter name' implies either tool works for the supported keys, leaving the choice slightly ambiguous.

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