FlaxMCP-Live

Overview Schema Source Related Servers Discussions Admin

editor_camera_screenshot

Capture a PNG from a chosen camera, even with the editor covered or minimized, in play or edit mode. Renders the 3D scene with post effects and no UI.

Instructions

Renders a camera into its own render target and saves a PNG. It does not read an editor window, so it works with the editor covered, small or minimised, in play mode and in edit mode. Camera: the given Camera actor. Without one: the main camera in play mode, else the editor viewport's view. The picture shows the 3D scene with the game's post effects, without editor or screen-space UI. Not available in headless mode. Replaces an existing file. Read the PNG to see it.

Input Schema

Name	Required	Description
`path`	Yes	Absolute or current-working-directory-relative output path ending in .png. The folder must exist.
`width`	No	Picture width in pixels, 16..8192.
`height`	No	Picture height in pixels, 16..8192.
`cameraId`	No	A Camera actor's id (from editor_scene_graph or editor_find_actors). Empty: the main camera in play mode, else the editor viewport's view.
`warmUpFrames`	No	Frames the camera renders before the capture, 1..60, so that auto exposure settles.

Output Schema

Name	Required	Description	Default
`path`	Yes
`bytes`	Yes
`width`	Yes
`camera`	Yes
`height`	Yes
`isPlayMode`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.1Nov 2, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses the destructive side effect ('Replaces an existing file'), the environment prerequisite (folder must exist, per schema), the unavailability in headless mode, and what the image will and will not contain (post effects included, editor and screen-space UI excluded).

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?

Front-loaded with the core action, then scope, then camera selection, then output characteristics, then constraints. Terse fragments are used deliberately and each sentence contributes a distinct fact; nothing is padding.

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

Completeness5/5

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

For a 5-parameter tool with an output schema (so return values need not be explained) and no annotations, the description covers action, scope, defaults, environment limits, and file side effects. An agent has everything needed to invoke it correctly, plus the 'Read the PNG to see it' hint that the result must be inspected separately.

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%, so the schema already documents path, width, height, cameraId and warmUpFrames with ranges and defaults. The description's camera sentence ('Camera: the given Camera actor. Without one: the main camera...') largely restates the cameraId schema text rather than adding new meaning. Baseline 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?

States a specific verb and resource: 'Renders a camera into its own render target and saves a PNG'. The follow-up clause 'It does not read an editor window' explicitly separates it from the sibling editor_screenshot, so an agent can route between them without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear when-it-works context (editor covered, small, minimised, play mode, edit mode) and an explicit exclusion ('Not available in headless mode'), plus the default camera selection rule. It stops short of naming the alternative tool (editor_screenshot) outright, so the alternative is implied rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server