Skip to main content
Glama

scene_cut_detect

Detects scene cuts in the current timeline and razors clips at each cut, making flattened masters easier to edit.

Instructions

Detect scene cuts in the current timeline and razor the clips at each cut (useful for flattened masters).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "scene_cut_detect"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. To its credit it explicitly discloses the mutating effect ('razor the clips at each cut'), which is the single most important behavioral fact here. It says nothing about whether the cuts are undoable, whether detection runs on the whole timeline or selection only, or how many edits may result, which is a meaningful gap for a destructive edit.

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

Conciseness5/5

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

A single front-loaded sentence that states the action and its use case with no filler. Nothing is redundant or buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters, no annotations and no output schema, the description is short but leaves a real gap: an agent cannot tell whether the razor operation is reversible, whether it creates a single undo step, or whether the detected cuts are reported back. For a destructive zero-param tool one more clause would have closed the loop.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly implies the operation is scoped implicitly to the current timeline.

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?

The description names a specific operation and resource: detect scene cuts in the current timeline and razor clips at each cut. An agent can tell this combines detection with an edit, not merely analysis. It does not distinguish itself from the sibling razor tool, which also cuts clips, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The parenthetical '(useful for flattened masters)' gives a legitimate use context, which is more than nothing. However, there is no explicit when-to-use/when-not guidance and no mention of the razor sibling as an alternative for manual cuts, leaving selection to inference.

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