UE5-MCP-Server

Overview Schema Source Related Servers Discussions Admin

ue5_spawn_actors_batch

Batch spawn multiple actors at specified transforms using a static mesh asset or actor class. Populate large scenes like forests.

Instructions

Spawns multiple actors in sequence. Useful for generating forests or large scenes quickly.

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": {
      "transforms": "<transforms>"
    },
    "name": "ue5_spawn_actors_batch"
  }
}

Input Schema

Name	Required	Description
`objectPath`	No	Asset path of the static mesh to spawn (Mutually exclusive with actorClass).
`actorClass`	No	Class path of the actor to spawn (Mutually exclusive with objectPath).
`transforms`	Yes	An array of transforms.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 18, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description must carry the full burden of behavioral disclosure. It mentions 'in sequence' but does not disclose critical details such as fail behavior, performance implications, or the mutual exclusivity of objectPath and actorClass (which is only in the schema).

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?

The description is two sentences with no wasted words. The purpose is front-loaded, followed by a usage context. It is appropriately concise.

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?

Given no output schema and moderate complexity (3 parameters, one required), the description is incomplete. It omits information about return values, error cases, and constraints like the mutual exclusivity of parameters, which are essential 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 the baseline is 3. The description adds no extra meaning beyond what the schema provides; it does not explain the distinction between objectPath and actorClass or the structure of transforms.

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?

The description clearly states the tool spawns multiple actors in sequence, distinguishing it from the sibling tool 'ue5_spawn_actor' which spawns a single actor. The verb 'spawns' and resource 'multiple actors' are specific.

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

Usage Guidelines3/5

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

The description provides a use case ('generating forests or large scenes quickly'), which implies when to use this tool over alternatives. However, it lacks explicit when-not-to-use guidance or comparison with other spawning methods.

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