Skip to main content
Glama

Read Shot Layer

lab_shots
Read-only

Read the SHOT layer of a sequence — which clips form one shot, which scene it plays in, who is in it, and what the continuity pass found. This is the layer above the timeline: lab_get_sequence gives you clips in a row, this one gives you the cut. Costs nothing, writes nothing. Use it before changing a cut: a shot binds clip_ids, so the times come out of the timeline and a shot whose clips you shorten simply gets shorter. Read clips_ohne_shot as well — it says how far the meaning lags behind the timeline, and an empty shots list usually means nobody has derived them yet (lab_shots_ableiten does that, for free). Every shot reports clips_verwaist (clip_ids that no longer exist in the timeline) and zusammenhaengend (false when another shot's clip sits between this one's): a torn shot is allowed — one location cut into twice — but it says so, instead of showing a duration longer than the sum of its clips.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rungNoWhich level to read. 'shot' (the default) is one take; 'movement' groups shots into arcs. They are independent layers over the same clips — reading one never shows the other
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.6/5.0
Behavior5/5

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

Annotations only say readOnlyHint=true; the description goes well beyond, promising 'Costs nothing, writes nothing' and explaining non-obvious semantics: shots bind clip_ids so shortening a clip shortens the shot, torn shots are permitted, and empty results mean derivation hasn't run. This is exactly the behavioral context annotations can't carry.

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?

Dense but front-loaded: purpose, cost, and usage come first. Every sentence carries information, though the closing clauses about continuity and torn shots are heavy and slightly rambling for the payoff they deliver.

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?

There is no output schema, so the description carries the return-value burden and does so: it names and explains clips_ohne_shot, clips_verwaist, zusammenhaengend, and the shots list. An agent knows what it will get and how to interpret edge cases.

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 coverage is 100% and the `rung` enum is already fully documented in the schema, including the shot-vs-movement distinction. The description discusses shot semantics but adds little about the two parameters themselves, so the baseline of 3 applies.

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?

Specific verb+resource: 'Read the SHOT layer of a sequence — which clips form one shot, which scene it plays in, who is in it.' It explicitly distinguishes itself from the sibling lab_get_sequence ('gives you clips in a row, this one gives you the cut'), so an agent can route without opening a schema.

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?

States when to use it ('Use it before changing a cut'), names the contrasting sibling (lab_get_sequence) and the derivation tool (lab_shots_ableiten). It also flags the empty-`shots` condition that routes the agent elsewhere. Alternatives and the trigger condition are explicit.

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