Skip to main content
Glama

Derive Shots from Scenes

lab_shots_ableiten
Idempotent

Derive the shot layer from what the clips already say about themselves — consecutive clips of the same scene become one shot, and a scene that returns later becomes a second one (one location cut into twice is two shots). Costs nothing: it groups rows and reads titles, it generates nothing. Titles come from the project's shotlist where the scene is in there, so this is more than a regrouping — it fetches meaning the pipeline already produced. SHOTS YOU SET BY HAND SURVIVE. Only derived ones are replaced, and clips already held by a manual shot are left out of the grouping entirely — a derivation does not take handwork's material away. Read clips_ohne_szene in the answer: those clips say nothing about where they belong, so each became its own shot. That number is a job for the pipeline, not a fault of this call — and grouping two nameless clips would be a claim about connection that nobody made.

Input Schema

NameRequiredDescriptionDefault
seq_idYesSequence id (from lab_create_sequence/lab_list_sequences) — positive integer as string

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

A4/5.0
Behavior5/5

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

Goes well beyond the annotations by defining the mutation boundary precisely: only derived shots are replaced, manual shots and their clips are excluded from grouping, and no generation/compute occurs. That is exactly the information an agent needs before invoking a non-readOnly, idempotent operation.

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

Conciseness3/5

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

The core rule is front-loaded, but the text is prose-heavy and padded with editorializing ('a claim about connection that nobody made', 'a job for the pipeline, not a fault of this call'). The valuable clips_ohne_szene explanation is buried near the end.

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?

With no output schema, the description usefully explains the one response field (clips_ohne_szene) and its meaning, and covers preservation semantics. It leaves minor gaps such as preconditions (e.g., must clips already exist) and the returned shape overall.

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?

The single seq_id parameter is fully documented in the schema (100% coverage, including its source tools), and the description adds nothing about it. Baseline 3 is appropriate when the schema carries all parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource (derive the shot layer) and spells out the grouping rule — consecutive same-scene clips merge, a returning scene yields a second shot. It implicitly separates itself from lab_shots_setzen via 'SHOTS YOU SET BY HAND SURVIVE', but never names that sibling explicitly.

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?

Clear context for when the call applies: clips must carry scene information, and clips without it come back in clips_ohne_szene rather than being grouped. It stops short of an explicit 'use lab_shots_setzen instead for manual shots' routing statement.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources