Skip to main content
Glama

spawn_scene_capture_2d

Spawn a SceneCapture2D actor in the Unreal Editor world and report whether its capture component has a UTextureRenderTarget2D assigned.

Instructions

Spawns a SceneCapture2D actor into the editor world. Reports whether the capture component already has a UTextureRenderTarget2D assigned (has_render_target).

Returns: { actor_name: string, actor_internal_name: string, actor_class: string, has_component: bool, has_render_target: bool, spawned: bool }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locationNoOptional [X, Y, Z] world location (defaults to origin)
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)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive, non-open-world spawn. The description adds behavioral value by disclosing the has_render_target check, which tells the agent the returned component may or may not already be wired to a UTextureRenderTarget2D. It doesn't say whether the spawn is undoable or what happens on repeat calls, so it only modestly exceeds the annotation floor.

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

Conciseness4/5

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

Front-loaded with the core action in the first sentence, followed by a compact behavioral note and an explicit return field list. It is efficient, though the enumerated return keys are somewhat list-like rather than prose.

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

Completeness4/5

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

With no output schema, the description usefully enumerates the return fields and flags the has_render_target signal, and the annotations cover the safety profile for this mutating spawn. Remaining gaps (permissions, undo behavior, repeat-call semantics) are minor for a spawn tool.

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%, including unit/format detail (object vs. array rotation, axis ordering) and defaults, so the schema already carries the parameter semantics. The description adds nothing about location or rotation, making 3 the correct baseline.

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 definition states a specific verb and resource: 'Spawns a SceneCapture2D actor into the editor world.' This cleanly separates it from the read/write siblings (get_scene_capture_2d_properties, set_scene_capture_2d_properties) and from other spawn_* tools, but it stops short of naming any alternative or contrasting its scope with the more generic spawn_actor.

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 when-to-use or when-not-to-use guidance, no mention of prerequisites, and no reference to sibling tools such as spawn_actor or spawn_blueprint_actor. The agent must infer usage entirely from the verb and actor class.

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