Skip to main content
Glama

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 and lighting, 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 and one lighting setup 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

TableJSON 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
    • addedInput schema / additionalProperties
      Added value: +false
  2. 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"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / gruppe / enum
      Previous value: -[
-  "winkel",
-  "kadrage",
-  "komposition",
-  "bewegung"
-]New value: +[
+  "winkel",
+  "kadrage",
+  "komposition",
+  "bewegung",
+  "licht"
+]
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true. The description goes well beyond: it explains that schluessel fragments are appended verbatim and not rewritten, that handwerk=true toggles an extra payload, and that it is read-only and free. These are substantive behavioral traits not derivable from annotations.

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 condition and follows with structured detail. It is dense and long but each clause (effect keys, three-key limit, stacking rules, handwerk behavior) carries distinct information, so it earns its length despite being near the upper bound.

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 3-param, no-required, no-output-schema tool, the description covers purpose, triggering intent, parameter semantics, the handoff to lab_prompt_transform, composition constraints, and the optional handwerk payload. Nothing an agent needs to invoke it correctly is absent.

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 baseline is 3, but the description adds real meaning: it gives example wirkung values (bedrohung, isolation, sehnsucht), clarifies gruppe limits to one group, and explains that handwerk returns camera craft. It enriches the enum/boolean semantics beyond the schema text.

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 (directing techniques library) and explicitly names the triggering user intent — asking HOW to stage/shoot a feeling. It clearly distinguishes itself from the processing sibling lab_prompt_transform by describing the search-vs-apply handoff.

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?

Explicit when-to-use ('person asks HOW to stage or shoot a feeling or effect'), names the downstream alternative lab_prompt_transform and the exact call shape, and gives composition rules (one angle, one movement, one lighting per shot; framing and composition stack) that select correct usage.

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