Skip to main content
Glama

unreal_add_camera

Add a camera to an Unreal Engine level or sequence to set up viewing angles for cinematics, gameplay, or scene capture.

Instructions

Add a camera to the level/sequence.

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

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?

With no annotations, the description carries the full behavioral burden. 'Add' implies mutation, but it does not state what kind of camera is created (actor, component, cine camera), what side effects occur, whether it is undoable, or whether it requires an open sequence. It is not contradictory, just thin.

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?

One front-loaded sentence with no wasted words, which is structurally fine. The brevity crosses into under-specification given the opaque parameter object and absent annotations.

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 undocumented parameter bag, the description omits what an agent needs to invoke it correctly: parameter shape, target context, and side effects.

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 single parameter is an opaque 'params' object with 0% schema description coverage and no declared properties. The description adds no information about what must be supplied in it, so an agent has no way to know the expected shape from either source.

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 names a specific verb and resource with scope: 'Add a camera to the level/sequence.' An agent can tell this creates a camera object in a level or sequence context. It does not, however, distinguish itself from close siblings such as unreal_add_camera_cut, unreal_setup_camera, or unreal_set_viewport_camera.

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 guidance, no prerequisites (must a level or sequence be open?), and no mention of the sibling tools that also create or configure cameras. The phrase 'level/sequence' hints at two contexts but never says which to choose or what happens if neither is active.

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