Skip to main content
Glama

unreal_add_camera_cut

Add a camera cut to an Unreal Engine sequence to switch between camera shots during cinematic playback.

Instructions

Add a camera cut.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/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 discloses nothing: not whether this mutates a level or sequence, what permissions or prior setup are required, nor what happens on failure. Nothing beyond the tool name is conveyed.

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

Conciseness2/5

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

It is short, but short due to under-specification rather than disciplined editing; there is no front-loaded purpose statement or structure to speak of. Brevity here is a liability, not a virtue.

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

Completeness1/5

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

For a mutation tool with an opaque object parameter, no annotations, and no parameter documentation, the description is wholly inadequate. The existence of an output schema removes the need to explain return values, but that does not offset the missing input and behavior information.

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 required parameter 'params' has 0% schema description coverage and is an untyped object, and the description says nothing about its contents or expected shape. This is the worst case for parameter documentation — the agent has no way to construct a valid call.

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

Purpose2/5

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

"Add a camera cut" is essentially a restatement of the tool name, with no definition of what a 'camera cut' is in this context. It does not distinguish itself from siblings like unreal_add_camera or unreal_set_viewport_camera, so an agent cannot tell which to choose from the text alone.

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 mention of alternatives such as unreal_add_camera or unreal_setup_camera. The agent is left to guess the tool's role entirely from the name.

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