FilmLab

Storage Location

lab_speicherort

Read or set where a project's generated material is kept. With project_id only: read. 'cloud' keeps it in FilmLab's private storage (default). 'lokal' and 'server' keep it private until publication: FilmLab only parks each new file for pickup, the local FilmLab bridge (DaVinci Resolve panel, FilmLab Drop for Final Cut Pro, Avid and Premiere Pro, or filmlab_abholen in the local bridge MCP) stores it on this computer ('lokal') or the studio's shared storage such as a NAS or Avid NEXIS ('server'), checks it and confirms. FilmLab keeps a private working copy (never public, signed access only) so export, sound mix and chains keep working, and deletes it when the project is closed with abschliessen: true, or when the period ends. Use 'lokal' or 'server' whenever the person wants generated material to stay off the cloud until release. The change applies to material generated from now on. abschliessen: true (only after the person confirms the project is finished or published) deletes all working copies at FilmLab; it is refused while files are still waiting for pickup unless auch_offene: true, which deletes those for good. The answer carries speicherort, privat, offen (files still waiting for pickup), arbeitskopien (copies FilmLab still holds), abholfrist_tage (after that, working copies are deleted) and a sentence to pass on.

Input Schema

Name	Required	Description
`project_id`	Yes	Project id (from lab_list_projects)
`auch_offene`	No	With abschliessen: also delete files that were never picked up (they are then gone for good)
`speicherort`	No	'cloud', 'lokal' (this computer) or 'server' (studio storage). Omit to only read
`abschliessen`	No	true: the project is finished — delete all of FilmLab's working copies. Ask the person first

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 31, 2026

addedInput schema / properties / abschliessen

Added value: +{
+  "description": "true: the project is finished — delete all of FilmLab's working copies. Ask the person first",
+  "type": "boolean"
+}

addedInput schema / properties / auch_offene

Added value: +{
+  "description": "With abschliessen: also delete files that were never picked up (they are then gone for good)",
+  "type": "boolean"
+}

AddedOct 31, 2026

TDQS

A3.8/5.0

Behavior1/5

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

The description explicitly states that abschliessen: true deletes all working copies at FilmLab, and that auch_offene: true deletes never-picked-up files for good. This contradicts the annotation destructiveHint: false, which tells the agent the tool is non-destructive. The description is otherwise detailed, but the annotation contradiction forces a score of 1.

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?

The description is front-loaded with the read-versus-set distinction and then explains storage modes and deletion behavior. It is long and dense, but most sentences carry necessary operational detail. Slightly better paragraphing or bullets would improve readability, so it is not a 5.

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 four-parameter tool with no output schema, the description covers the read/write modes, storage semantics, deletion rules, confirmation requirements, and even the fields returned in the answer. An agent has enough context to invoke it correctly, apart from the annotation inconsistency.

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 description coverage is 100%, so the baseline is 3. The description adds meaningful cross-parameter semantics beyond the schema: 'cloud' is the default, 'lokal' and 'server' require pickup by a local bridge, and auch_offene only matters with abschliessen and permanently deletes unpicked files. This is useful inter-parameter guidance not fully captured by the individual schema descriptions.

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?

The description states a specific verb and resource: reading or setting where a project's generated material is kept. It also distinguishes read mode from write mode based on whether speicherort is supplied, so an agent can understand the operation without opening the 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?

It gives clear conditions for using 'lokal' or 'server' versus 'cloud', and explicitly says abschliessen should only be used after the person confirms the project is finished. It also specifies the refusal condition for open files and the auch_offene override. It does not name sibling tools as alternatives, keeping it below a 5.

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?