FilmLab

VFX Operation

lab_vfx

Run a VFX operation on an image already in the project gallery — the same pipeline the Resolve bridge uses. inpaint (clean plate: what is inside the box disappears, the surroundings close over it) · replace (same path, other intent: something new goes into the box) · relight (no box — the light changes across the whole frame; by default the scene stays exactly as it is, licht_weg 'iclight' instead repaints the background and may change the scenery) · mask (no box — you describe what should be cut out and get the matte back). inpaint/replace need box AND prompt; relight needs light_preset or prompt and REJECTS a box; mask needs prompt and REJECTS a box too. box is given in FRACTIONS of the image (0..1), not pixels — the worker builds the mask. inpaint/replace start at 5 credits per run on the reference area (larger areas cost more); relight costs 4 flat per image (licht_weg 'iclight': from 9, by area); mask costs 1, flat per request. Returns immediately with an operation_id; poll lab_vfx_status until status is done|failed. NOT offered here: composite, move, color_grade — the server knows them and has no consumer for them.

Input Schema

TableJSON Schema

Name	Required	Description
`box_x`	No	Box left edge as a fraction of image width (0..1)
`box_y`	No	Box top edge as a fraction of image height (0..1)
`prompt`	No	inpaint/replace: what should be seen there instead — required. mask: what should be cut out (e.g. 'the red toolbox') — required. relight: optional, replaces the preset
`image_id`	Yes	Id of the source image in the project gallery (from lab_list_assets / lab_generate)
`box_hoehe`	No	Box height as a fraction of image height
`licht_weg`	No	relight only. kontext (default): only the light changes, scene, people and framing stay. iclight: the background is repainted from the light description — the scenery may change
`operation`	Yes	inpaint: Die rote Werkzeugkiste wird durch eine Holzkiste auf der Werkbank ersetzt. \| replace: Derselbe Weg, andere Absicht: in die Box kommt etwas Neues. \| relight: Keine Box: die Lichtrichtung wandert über das ganze Bild. \| mask: Keine Box: du beschreibst, was heraus soll, und bekommst die Maske.
`box_breite`	No	Box width as a fraction of image width
`project_id`	Yes	Project id (from lab_list_projects)
`light_preset`	No	relight only. There is no 'bottom' — the server does not carry one

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 11, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

Changed1 schema field changedOct 5, 2026

addedInput schema / properties / licht_weg

Added value: +{
+  "description": "relight only. kontext (default): only the light changes, scene, people and framing stay. iclight: the background is repainted from the light description — the scenery may change",
+  "enum": [
+    "kontext",
+    "iclight"
+  ],
+  "type": "string"
+}

First observedOct 3, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations are minimal (readOnly false, destructive false), so the description carries the load and does so well: it discloses credit costs per operation (5/4/1, iclight from 9), the async contract (returns operation_id, poll lab_vfx_status until done|failed), the default non-destructive relight behaviour vs the iclight repaint, and box-rejection rules.

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-loaded with the action and then a dense but scannable operation breakdown separated by '·'. Every clause carries information, though the single long paragraph is heavy and could be slightly tighter for a 10-parameter tool.

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?

With no output schema, the description still tells the agent what comes back (operation_id) and how to follow up, plus cost, defaults and per-operation input rules. Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: box is 'in FRACTIONS of the image (0..1), not pixels — the worker builds the mask', and it cross-links which params each operation demands. That exceeds what the per-field schema strings convey.

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 ('Run a VFX operation on an image already in the project gallery') and then decomposes the four operations with distinct meanings (inpaint removes, replace inserts, relight changes light, mask returns a matte). It also names the sibling to poll (lab_vfx_status) and explicitly excludes composite/move/color_grade, so an agent can separate it from neighbours like lab_vfx_preset.

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 per-operation requirements: inpaint/replace need box AND prompt, relight needs light_preset or prompt and rejects a box, mask needs prompt and rejects a box. It also states what is NOT offered here, which is exactly the kind of exclusion that steers an agent to the right tool.

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

All FilmLab tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?