Skip to main content
Glama
Sign In
unreal-mcp-additional-tools

unreal-mcp-additional-tools

by nodormu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

render_sequence

Queue a Movie Render Queue job for a specified LevelSequence asset, optionally setting an output directory to control where rendered frames are saved.

Instructions

Queue a Movie Render Queue job for a 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": {
      "sequence_path": "<sequence_path>"
    },
    "name": "render_sequence"
  }
}

Input Schema

NameRequiredDescriptionDefault
sequence_pathYesLevelSequence asset path
output_directoryNoOutput directory for rendered frames

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 carries the full burden of disclosing behavior, but it only says 'queue a job.' It does not indicate whether the operation is asynchronous, what happens on success or failure, or whether it returns any job identifier or status.

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 a single, direct sentence with no filler or redundancy. It is appropriately concise for the simple tool it describes.

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 annotations and no output schema, the description is minimal. It does not explain whether the call blocks, returns a job ID, or how to check status. Lacks essential behavioral context for an agent to use effectively.

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?

Both parameters (sequence_path and output_directory) have descriptions in the schema, fulfilling the baseline. The tool description itself adds no additional meaning or usage details beyond what's in the schema, so a baseline score of 3 is appropriate.

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

Purpose5/5

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

The description clearly states the action (queue a render job) and the specific resource type (Movie Render Queue) for a given sequence. It distinguishes from sibling tools like export_sequence_fbx or set_playback_range by focusing on the rendering queue workflow.

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?

No explicit guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, such as needing an open project or a valid sequence, nor does it contrast with other sequence-related tools that might be more appropriate for certain tasks.

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