Skip to main content
Glama

cut_shot

Split a shot into two at a chosen time so both parts replay exactly what the original played; the second keeps the transition and the voice stays in the first.

Instructions

Cut a shot in two at a time, like a clip in an editor: both parts together play exactly what the shot played; the second keeps the transition and the voice stays in the first. Times round to 0.1 s and must be at least 0.2 s from either edge. Returns { first, second } shot ids. One undo step for the person. To change only the length, use edit_project on seconds.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "at": "<at>"
    },
    "name": "cut_shot"
  }
}

Input Schema

NameRequiredDescriptionDefault
atYesSeconds into the shot where it's cut.
idNoShot id (left out: the shot on screen).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.2
    • changedInput schema / properties / at / description
      Previous value: -"Seconds into the shot."New value: +"Seconds into the shot where it's cut."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only say it is a non-destructive, non-idempotent write; the description goes well beyond them by disclosing that the second part keeps the transition, voice stays in the first, and the operation is a single undo step. The rounding rule (0.1 s) and minimum 0.2 s edge distance are also behavioral constraints an agent would otherwise trip over. Minor gap: no statement on what happens if a cut lands on an existing boundary.

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?

Two tight sentences front-load the operation, then the alternative. The middle clause about transitions and voice is dense but each clause carries distinct information; nothing is filler.

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?

With no output schema, the description supplies the return shape ('{ first, second } shot ids'), and it covers the constraints and side effects an agent needs to call this correctly. Nothing material for a 2-parameter split tool is missing.

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% and already documents both `at` and `id`, so baseline is 3. The description adds real semantics beyond the schema: times round to 0.1 s and must be at least 0.2 s from either edge, which constrains valid values in a way the schema does not.

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 and resource ('Cut a shot in two at a time') and reinforces it with a concrete analogy (clip in an editor), making the split semantics unambiguous. It also names the sibling that handles a superficially similar need (edit_project) so the agent can tell them apart immediately.

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?

Explicitly routes the adjacent use case away: 'To change only the length, use edit_project on seconds.' It does not spell out when-not to cut at all (e.g., locked shots or transitional edge cases), so it stops short of full when/when-not coverage.

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