Skip to main content
Glama

unreal_render_image

Render the current Unreal Engine view to an image file for visual inspection, sharing, or workflow capture.

Instructions

Render an image from the current view.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.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 behavioral burden and does not meet it. It does not state whether the image is written to disk or returned inline, what format/resolution is used, whether it blocks while rendering, or what "current view" means when no viewport is focused.

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 short sentence with no filler, so nothing is wasted, but the brevity reflects under-specification rather than efficient communication. The most decision-relevant information (output destination, distinction from capture tools) is simply absent.

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 described, but that is the only relief. For a render tool with a mandatory opaque parameter block and no annotations, the definition leaves the agent without enough information to invoke it correctly or choose it over sibling capture/render tools.

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 is an opaque, untyped "params" object with 0% schema description coverage, and the description adds nothing about its contents. An agent has no way to know what must be supplied to invoke the tool successfully.

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?

"Render an image from the current view" gives a verb and a resource, but the purpose overlaps heavily with siblings such as unreal_capture_screenshot, unreal_capture_viewport and unreal_render_sequence. The description never says whether this is a single frame, whether it writes a file, or how it differs from those capture tools, so an agent cannot confidently pick it.

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 (e.g. an active editor viewport or render session), and no mention of the obvious alternatives. The agent must infer selection purely 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