Skip to main content
Glama

add_ism_instance

Place a mesh instance into an InstancedStaticMeshComponent at a world transform to scatter many copies cheaply without spawning an actor per copy. Requires an existing ISM component.

Instructions

Place one more instance of an InstancedStaticMeshComponent's mesh at a world transform -- the cheap way to scatter many copies of a mesh (rocks, props, vegetation) without spawning an actor each. Pair it with add_instanced_static_mesh_component to create the component first. Prefer this route over the foliage tools: scatter_foliage_in_box and add_foliage_instances both CRASH the editor in this build, and an ISM is the same code path a foliage actor and PCG use anyway.

Returns: { instance_index: int, num_instances: int }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scaleNoOptional [x, y, z] scale (defaults to [1,1,1])
locationNo[x, y, z] world-space translation (required)
rotationNoPREFERRED: the OBJECT {"roll":R,"pitch":P,"yaw":Y} (any subset, absent axes are 0). The ARRAY form below is [pitch, yaw, roll] -- its index 2 is ROLL, NOT yaw, which once put a PlayerStart on its side. Optional [pitch, yaw, roll] world rotation (defaults to zero)
actor_nameYesDisplay label or internal name of the actor carrying the ISM component (required)
world_spaceNoOptional; if true, transform is interpreted in world space (default true)
component_nameNoOptional ISM component name (defaults to the first one on the actor)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare mutation, non-idempotence, and non-destructiveness, but the description adds substantive operational context beyond them: the additive 'one more instance' semantics, the required component-creation prerequisite, the editor-crash warning for competing foliage tools, and the returned instance counts. No annotation contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the operation, followed by the valuable prerequisite and alternative-tool warning, then the return shape. Every sentence contributes distinct information and none repeats the tool name or schema unnecessarily.

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?

Covers the behavioral prerequisite, the safe alternative, and the return shape even though no output schema exists. For a mutating ISM tool with full parameter coverage and annotations present, nothing important is missing for correct invocation.

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 description coverage is 100%, so parameter documentation is already carried by the schema, including a detailed warning about the rotation array ordering. The description adds only the high-level 'world transform' framing and does not elaborate on individual parameters beyond what the schema provides, so baseline 3 is appropriate.

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 precise verb and resource ('Place one more instance of an InstancedStaticMeshComponent's mesh at a world transform') and distinguishes the tool from its siblings by naming add_instanced_static_mesh_component and the foliage alternatives. The agent can identify exactly what operation this performs 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 Guidelines5/5

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

Gives explicit sequencing guidance ('Pair it with add_instanced_static_mesh_component to create the component first') and a clear preference rule with reasons ('Prefer this route over the foliage tools: ... both CRASH the editor in this build'). This is exactly the when-to-use and when-not-to-use guidance an agent needs.

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