Skip to main content
Glama
Immersive-Media-Technologies

AE-MCP

by Immersive-Media-Technologies
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Render frame

ae_render_frame

Render a single frame to PNG. Use to visually verify edits. The agent's 'eyes' — pair with mutations for a visual feedback loop. Headless and deterministic.

Instructions

Render a single frame to PNG. Use to visually verify edits. The agent's 'eyes' — pair with mutations for a visual feedback loop. Headless and deterministic. In color-managed projects (workingSpace != None) the capture applies AE's own display transform via a transient OCIO Display Transform adjustment layer, and the PNG comes back viewer-accurate and sRGB-tagged. Where that layer cannot be used — read-only mode, an AE without the OCIO effect, or a failed capture calibration — the result falls back to a pure-math ACES conversion or to raw values with an explicit colorWarning; check colorPipeline / colorWarning on the response.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timeYesTime in seconds to render.
outPathYesAbsolute path to write the PNG. Parent directory is created if missing.
compareWithNoAbsolute path of an earlier PNG (same comp size) to compare the new frame against. Adds `compare`: changedRatio (0..1 of pixels that differ), meanAbsDiff (0..1), bbox of the change — 'did my edit change the picture, and where' without reading the image.
colorManagedNo'auto' (default): detect the working space and return a viewer-accurate, 8-bit sRGB-tagged PNG. 'off': raw legacy output (16-bit, untagged, working-space values — dark/wrong-looking in color-managed projects).
compNameOrIdYesComposition name or numeric item id.
useDisplayStartTimeNoIf true, `time` is interpreted relative to comp.displayStartTime. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.5
    • addedInput schema / properties / compareWith
      Added value: +{
+  "description": "Absolute path of an earlier PNG (same comp size) to compare the new frame against. Adds `compare`: changedRatio (0..1 of pixels that differ), meanAbsDiff (0..1), bbox of the change — 'did my edit change the picture, and where' without reading the image.",
+  "type": "string"
+}
  2. First observedv0.4.2

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare destructiveHint=false, so the description carries the behavioral load and does so richly: headless, deterministic, and a detailed account of the color-management path (OCIO display transform, ACES fallback, raw-values fallback with explicit colorWarning). It even tells the agent to inspect colorPipeline/colorWarning on the response.

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

Conciseness4/5

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

Front-loads the core purpose in the first sentence, then layers the color-management caveats. It is longer than a typical description but most sentences earn their place given the non-obvious color fallback semantics; the dense final sentence is justified by real behavior variance.

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

Completeness4/5

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

For a 6-param tool with no output schema and only a single annotation, the description covers the important hidden behavior (headless determinism, color fallback, response fields to inspect). The absence of an output schema is offset by naming colorPipeline/colorWarning, though exact return shape is left implicit.

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 each parameter already documents its own meaning (time, outPath, compareWith, colorManaged, compNameOrId, useDisplayStartTime). The description explains the color pipeline behavior behind colorManaged='auto' vs 'off' but adds no syntax or format detail beyond the schema. 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+resource (render a single frame to PNG) and immediately scopes intent: 'Use to visually verify edits. The agent's eyes.' This clearly differentiates it from the many info/do/catalog siblings in the toolset.

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-to-use context (pair with mutations for a visual feedback loop, verify edits) but does not name explicit alternatives or when-not-to-use conditions. The context is strong for a specialized tool whose siblings are largely non-overlapping, but it stops short of an explicit routing rule.

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