Skip to main content
Glama

set_hlod_layer_actors

DestructiveIdempotent

Assign or clear a UHLODLayer for a batch of loaded actors in the current editor world. World Partition only.

Instructions

Assign a UHLODLayer to a BATCH of loaded actors in the current editor world -- or clear it from them by passing hlod_layer_path="". WORLD PARTITION ONLY: on a non-WP world it returns not_applicable=true and changes nothing. Idempotent per actor: one that already has that layer is not touched at all and comes back counted as unchanged, so the changed/unchanged/cleared split tells you exactly what really moved.

Returns: { hlod_layer_path, world, is_world_partition, not_applicable, note?, requested: int, changed: int, unchanged: int, cleared: int, not_found: [paths], changed_actors: [{actor_path, old_hlod_layer, new_hlod_layer}] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actor_pathsYesJSON array of actor paths (long package paths or object paths) to assign.
hlod_layer_pathNoFull /Game path of the UHLODLayer asset. Pass empty string ("") to clear.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare idempotentHint and destructiveHint, and the description goes further: it explains the exact idempotency semantics ('one that already has that layer is not touched at all and comes back counted as unchanged') and the world-partition gating behavior. It documents the full return shape including the changed/unchanged/cleared split, which is not in annotations.

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?

Dense but front-loaded: the core action and WP constraint come first, then idempotency, then the return schema. Slightly long, but every clause conveys distinct operational information, so it earns its size.

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

Completeness5/5

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

For a mutating, WP-gated tool with no output schema, the description supplies the safety profile, gating behavior, idempotency semantics, and a full return field enumeration. Nothing an agent needs to call and interpret it is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline 3. The description adds meaningful semantics beyond the schema: the empty-string clearing convention for hlod_layer_path and the batch semantics of actor_paths. It reinforces but doesn't fully re-specify parameter formats.

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 (assign/clear) and resource (UHLODLayer on a batch of loaded actors) with explicit scope ('in the current editor world'), and clarifies the clearing mode via hlod_layer_path="". An agent can distinguish this from sibling set_hlod_layer_parent or create_hlod_layer without opening the 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?

The 'WORLD PARTITION ONLY' constraint and the non-WP behavior (returns not_applicable=true, changes nothing) give clear when/when-not guidance. It does not name alternative tools for HLOD assignment, but the usage context is explicit.

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

Deploy Server

Other Tools