Skip to main content
Glama

unreal_validate_actor_placement

Validates actor placement in Unreal Engine levels to catch invalid positions before editing or running workflows.

Instructions

Validate actor placement.

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": {
      "params": "<params>"
    },
    "name": "unreal_validate_actor_placement"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden and provides none of it: it does not state whether the call is read-only, what happens when placement is invalid (error vs. report), or whether anything in the level is modified. The presence of an output schema covers return values, but the operation's side-effect profile is undocumented.

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

Conciseness3/5

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

The sentence is short and front-loaded with the action, with zero filler. Its brevity is under-specification rather than efficiency, so it earns a middle score.

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

Completeness3/5

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

The output schema means return values need not be explained, which keeps this from being fully inadequate. Still, for a validation tool the description omits the validation criteria and the shape of the opaque params object, leaving real gaps for a one-parameter call.

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?

The single parameter is an untyped "params" object with 0% schema description coverage, and the description adds nothing about what belongs inside it. With one opaque parameter and no compensation in the text, the agent cannot know how to address the actor being validated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description pairs a specific verb ("Validate") with a resource ("actor placement"), which separates it from siblings like unreal_validate_assets or unreal_validate_blueprints. However, it never says what aspect of placement is validated (collision, bounds, overlap, navigation), so the actual check remains vague.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no guidance on when to run this validation, no prerequisites (e.g., must the actor exist or be in a loaded level?), and no mention of alternatives or follow-up actions. The agent must infer usage entirely from the tool name.

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