Skip to main content
Glama

unreal_duplicate_actor

Duplicates an existing actor in an Unreal Engine 5 level, creating a copied instance you can then reposition or edit through the editor bridge.

Instructions

Duplicate an actor.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden, and it discloses nothing about behavior beyond 'duplicate'. It does not say whether the copy is placed at the same transform, whether the duplicate is selected/registered in the level, whether it is transactional/undoable, or what happens on failure.

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 verb, so there is no wasted wording. But its brevity is under-specification rather than concision; it could easily carry one more clause about input or effect.

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, and the tool is a simple one-parameter operation. Still, for a mutation tool with no annotations and a fully undocumented parameter, the agent lacks the minimum needed to call it correctly.

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?

Schema description coverage is 0% and the single 'params' property is an untyped object with no documentation at all. The description does not say what goes into params (an actor path? a name? a transform offset?), so the one parameter is completely opaque.

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 states a specific verb+resource ("Duplicate an actor"), which distinguishes it from read/delete siblings like unreal_delete_actor or unreal_find_actor. However, it does not distinguish it from unreal_duplicate_asset or from unreal_spawn_actor, which are plausible alternatives for creating a new actor instance.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no prerequisites, and no named alternative. The agent must infer entirely from the name that this copies an existing actor versus spawning a new one.

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