Skip to main content
Glama

gaps_close

Close an empty gap on a timeline track by specifying start/end or letting it target the first gap; later clips ripple left per Resolve rules.

Instructions

Close an empty gap on a track (ripple — later clips shift left; how other tracks react follows Resolve's ripple-delete rules). Give the gap with start/end, or omit them to close the FIRST gap found on the track.

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": "gaps_close"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
startNo
trackNoV1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries full burden and does disclose the key non-obvious effect: a ripple delete that shifts later clips left and defers cross-track effects to Resolve's ripple-delete rules. It omits whether the operation is undoable, what happens if no gap exists, and what the tool returns or reports.

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 with the core action front-loaded and the fallback behavior placed second. The parenthetical ripple clause is dense but each element carries information; nothing is filler.

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?

For a three-parameter mutation with no annotations and no output schema, the definition covers the action and its side effect but leaves the track argument, empty-track/no-gap edge cases, and post-call state unaddressed. Adequate to attempt a call, not complete enough to predict its result.

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 description coverage is 0%, so the description must compensate. It does clarify that start/end denote the gap boundaries and that both can be omitted, but the 'track' parameter (default 'V1') is never explained — format, scoping, or whether it must name a video vs audio track is left entirely to guesswork.

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 and object — close an empty gap on a track — and immediately clarifies the resulting edit (ripple left). It is clearly not a clip tool, but it never names or contrasts itself with any sibling, so differentiation is by inference from the verb.

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 description explains the two calling modes (supply start/end, or omit both to close the first gap), which is genuine usage guidance. It gives no when-not guidance, no prerequisites, and no pointer to any alternative tool for related gap or clip operations.

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