Skip to main content
Glama

unreal_spawn_actor

Adds a new actor to the current Unreal Engine 5 level, letting AI clients place objects or gameplay elements directly in the open scene.

Instructions

Spawn an actor in the current level.

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_spawn_actor"
  }
}

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 provided, so the description carries the full behavioral burden and largely drops it. It does not say what class/asset the spawned actor comes from, what transform or defaults it receives, whether the action is undoable, or what permissions or editor state are required. Only the 'current level' scoping hint adds anything beyond the name.

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 single sentence is tight and front-loaded with the verb, with no wasted wording. However, the brevity here reflects under-specification rather than efficient communication, since key invocation information is simply absent.

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

Completeness2/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. But for a mutation tool with no annotations and a completely opaque required 'params' object, the definition leaves the agent unable to construct a valid call, which is a significant completeness gap.

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

Parameters1/5

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

The tool takes one required parameter named 'params' with 0% schema description coverage and no type detail beyond an empty object, so the schema gives the agent nothing to work with. The description never mentions the parameter at all, leaving the agent with no idea what fields to populate — the precise case the description is supposed to compensate for.

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

Purpose4/5

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

States a specific verb (spawn) and resource (actor) plus the target scope (current level), so the agent knows exactly what operation is performed. It does not distinguish itself from nearby spawn-family siblings such as unreal_spawn_niagara_system or explain how it differs from unreal_duplicate_actor, so it stops short of a 5.

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 use this versus duplicating an existing actor or spawning a Niagara system, no prerequisites (does a level need to be open, must an asset path be supplied), and no statement of what happens on failure. The single sentence is a statement of purpose, not usage guidance.

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