Skip to main content
Glama

editor_screenshot

Captures the running Flax Editor Scene viewport to a PNG file for visual verification. Requires the Scene tab visible, an existing output folder, and non-headless mode.

Instructions

Captures the Scene viewport of the running Flax Editor to a PNG file. The Scene tab must be visible: the capture fails when another tab covers it. The output folder must exist. The capture is not available in headless mode. To render from a camera without the Scene tab, use editor_camera_screenshot.

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": {
      "path": "<path>"
    },
    "name": "editor_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute or current-working-directory-relative output path ending in .png.

Output Schema

NameRequiredDescriptionDefault
pathYes
bytesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4.5/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does well: it discloses the tab-visibility requirement, the failure mode when covered, the folder-existence prerequisite, and the headless-mode limitation. Only minor gaps remain, such as whether an existing file at the path is overwritten and any latency or resolution caveats; return values are covered by the output schema.

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?

Five short sentences, front-loaded with the action and followed by the failure conditions and the alternative routing. No filler or redundancy; every sentence carries operational information.

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 single-parameter capture tool with an output schema, the description covers the environment constraints, failure conditions, and the sibling alternative. An agent has everything needed to decide whether and how to call it.

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% and the single path parameter is already documented as an absolute or CWD-relative .png path. The description adds nothing about path handling beyond what the schema states, so the baseline 3 applies.

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 concrete verb and resource ("Captures the Scene viewport of the running Flax Editor to a PNG file") and explicitly distinguishes itself from the sibling editor_camera_screenshot. An agent can tell immediately what it does and how it differs from the camera-based alternative.

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

Usage Guidelines5/5

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

Gives explicit preconditions (Scene tab must be visible, the capture fails otherwise, output folder must exist, not available in headless mode) and names the alternative for the case where those conditions don't hold. This is exactly the when-to-use / when-not-to-use / alternative structure.

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