Skip to main content
Glama

dissolve

DestructiveIdempotent

Adjust or remove a crossfade at a video clip join. Specify the incoming clip and its start time; set seconds to zero to cut. Use plan to preview without writing.

Instructions

Set, change or clear the crossfade at a join follow made.

Addressed by the incoming clip and where it starts there, never a timeline second, so a cut elsewhere moves it. seconds=0 makes the join a cut again. Checked against the timeline before writing; plan=true writes nothing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
easeNoThe crossfade's curve: linear (the default), ease, ease-in or ease-out.linear
pathNoThe project directory to act on. Omit it — the usual case — when this server is bound to a project (started as `proofcut -C DIR mcp`, or inside a project; `ping` says which): it then resolves to that one bound project, a relative path resolves against it, and a path outside it is refused by name. Unbound, `path` is the whole address and omitting it refuses rather than guessing.
planNoResolve the whole call and report what it would do, writing nothing. Prefer it over doing the thing and undoing it.
clip_idYesThe incoming clip of a join `follow` made.
secondsYesSeconds of crossfade; 0 clears it back to a cut.
src_startYesWhere clip_id starts at that join, in its own seconds (follow's reply says).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.37.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark the operation as destructive and idempotent, and the description adds meaningful behavior beyond that: addressing is tied to the incoming clip's start position so a cut elsewhere moves the dissolve, `seconds=0` restores a cut, and the call is 'checked against the timeline before writing.' This materially helps an agent predict side effects.

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?

The description is compact, roughly four sentences, and every sentence earns its place: the operation, the addressing model, the clearing behavior, and the safety/plan behavior. Key information is front-loaded.

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 moderately complex mutation with six fully documented parameters and an output schema, the description covers the essential context: how to reference the join, how to clear the crossfade, the validity check, and the plan mode for side-effect-free dry runs. Nothing needed for correct invocation 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%, so the baseline is 3, but the description adds a relationship between `clip_id` and `src_start` that the schema states only separately: the dissolve is addressed by incoming clip and its local start, never a timeline second. The `plan` parameter's dry-run behavior is also reinforced in context.

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?

The description opens with a specific verb phrase, 'Set, change or clear the crossfade at a join `follow` made,' identifying both the resource (a join created by `follow`) and the operation. It distinguishes itself from related timeline tools by explaining that the address is by incoming clip and source position, 'never a timeline second.'

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?

The description clearly frames when to use the tool: to modify a dissolve at a follow-created join, with `seconds=0` to return to a cut and `plan=true` for a dry run. It does not explicitly name sibling alternatives or state when not to use it, but the scope is concrete enough that an agent can select it appropriately.

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

Deploy Server

Other Tools