Skip to main content
Glama
Sign In

FilmLab

by com.thefilmradar
OverviewDiscussionsAdmin

Directing Techniques

lab_regie_techniken
Read-only

Use when the person asks HOW to stage or shoot a feeling or effect (which angle, movement, framing or light makes a scene feel tense, tender, triumphant, uneasy) or wants directing options for a shot. Directing techniques: camera angle, framing, composition, movement, lighting and atmosphere (haze, dust, embers, backlit rain), each with the emotional effect it creates (wirkung), when to use it (zweck_de), when it backfires (vermeiden_de) and a model-neutral prompt fragment (prompt_en). Search by effect (e.g. wirkung=bedrohung, isolation, sehnsucht) to find the ways to get there, then pass up to three schluessel to lab_prompt_transform(techniken) — the fragments are appended verbatim, not rewritten. One angle, one movement, one lighting setup and one atmosphere per shot; framing and composition stack. With handwerk=true it also returns the camera craft: how to state a shot so a model renders it (rules), look-alike pairs with a check sentence each (verwechslungen — e.g. low angle vs Dutch angle, OTS vs POV), focal lengths and the frame boundary of every shot size. Read-only, free.

Input Schema

NameRequiredDescriptionDefault
gruppeNoOnly one group
wirkungNoOnly techniques with this effect key — the answer lists all keys under `wirkungen`
handwerkNoAlso return the camera craft (rules, look-alike pairs, focal lengths, frame boundaries)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / gruppe / enum
      Previous value: -[
-  "winkel",
-  "kadrage",
-  "komposition",
-  "bewegung",
-  "licht"
-]New value: +[
+  "winkel",
+  "kadrage",
+  "komposition",
+  "bewegung",
+  "licht",
+  "luft"
+]
  2. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  3. Changed1 schema field changed
    • addedInput schema / properties / handwerk
      Added value: +{
+  "description": "Also return the camera craft (rules, look-alike pairs, focal lengths, frame boundaries)",
+  "type": "boolean"
+}
  4. Changed1 schema field changed
    • changedInput schema / properties / gruppe / enum
      Previous value: -[
-  "winkel",
-  "kadrage",
-  "komposition",
-  "bewegung"
-]New value: +[
+  "winkel",
+  "kadrage",
+  "komposition",
+  "bewegung",
+  "licht"
+]
  5. First observed

TDQS

A4/5.0
Behavior3/5

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

readOnlyHint=true is already in annotations, and 'Read-only, free' merely restates it without contradiction. The description does add real behavioral context: fragments are appended verbatim, not rewritten; handwerk=true additionally returns craft material (rules, look-alike pairs, focal lengths, frame boundaries); the response exposes the available effect keys under `wirkungen`. With annotations already covering safety, this is solid but not exhaustive (no pagination/volume expectations).

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 trigger sentence before the content inventory, and every sentence carries information (what it returns, how to consume the output, composing rules, handwerk extras). It is dense and parenthetical-heavy, though, reading closer to one long run-on block than cleanly separated guidance.

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?

No output schema exists, yet the description names the returned fields (wirkung, zweck_de, vermeiden_de, prompt_en), explains how to consume them downstream, and describes the optional handwerk payload. For a read-only 3-parameter lookup tool, an agent has everything needed to invoke it correctly.

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 all three parameters, including the handwerk behavior. The description adds useful example values for `wirkung` (bedrohung, isolation, sehnsucht) and hints at `gruppe` semantics via the per-shot categories, but does not elaborate the 'Only one group' constraint beyond the schema.

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 retrieval purpose (directing techniques for staging/shooting a feeling) and enumerates the exact resource contents: camera angle, framing, composition, movement, lighting, atmosphere, each with wirkung/zweck_de/vermeiden_de/prompt_en. The effect-key search plus prompt-fragment payload makes it clearly distinguishable from catalog tools like lab_wissen or lab_neue_winkel.

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 an explicit trigger ('Use when the person asks HOW to stage or shoot a feeling or effect') and a workflow: search by effect, then pass up to three `schluessel` to lab_prompt_transform(techniken). It also states practical composing rules (one angle, one movement, one lighting setup, one atmosphere per shot; framing and composition stack). It stops short of saying when NOT to use it versus a sibling.

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

All FilmLab toolsInspect
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