Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

video_reverse

Reverses video and audio playback so a clip plays backwards, with optional output path and overwrite control.

Instructions

Reverse video and audio playback so it plays backwards.

Args: input_path: Absolute path to the input video. output_path: Where to save the output. Auto-generated if omitted.

Input Schema

NameRequiredDescriptionDefault
overwriteNoExplicitly allow replacing existing media. Existing non-media files are protected.
input_pathYes
output_pathNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.16.4
    • addedInput schema / properties / overwrite
      Added value: +{
+  "default": false,
+  "description": "Explicitly allow replacing existing media. Existing non-media files are protected.",
+  "title": "Overwrite",
+  "type": "boolean"
+}
  2. Changed1 schema field changedv1.16.0
    • addedInput schema / additionalProperties
      Added value: +false
  3. Addedv1.5.1

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does add real behavioral information beyond the schema: both video AND audio are reversed (a non-obvious side effect), and the output path is auto-generated when omitted. It omits re-encode/quality implications, format limits, metadata preservation, and runtime cost, which matter for a media transform.

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?

The purpose sentence is front-loaded and waste-free. The Args block is slightly boilerplate but earns its place given the two undocumented parameters, though it adds no value for overwrite.

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?

An output schema exists, so return values need not be explained. For a 3-parameter transform tool this is close to adequate, but with zero annotations an agent still lacks guidance on overwrite semantics, format constraints, and whether audio reversal is unconditional.

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 only 33% (input_path and output_path are undocumented in the schema). The description compensates by stating input_path is an absolute path and output_path is optional/auto-generated, and overwrite is well covered by the schema itself. Together all three parameters are explained, but with no depth on formats or path resolution rules.

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 gives a specific verb and resource: reverse video and audio playback so it plays backwards. That is unambiguous and clearly distinct from neighbors like video_trim, video_convert, or video_rotate. It does not, however, name or rule out any sibling (e.g. video_speed with a negative factor), so 4 rather than 5.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus alternatives, no prerequisites, and no exclusions. The only contextual hint is the arg list, which tells the agent what to pass but not when this tool is the right choice among the many media-transform siblings.

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