Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

video_mograph_count

Generate an animated counting number video from a start value to an end value over a set duration. Create standalone motion graphics number counters with custom styling and frame rate.

Instructions

Generate animated number counter video.

Creates a standalone video of an animated counting number.

Args: start: Starting number. end: Ending number. duration: Animation duration in seconds. output_path: Absolute path for output video. style: Optional style dict with font, size, color, glow. fps: Frame rate. Default 30.

Returns: Dict with success status and output_path.

Input Schema

NameRequiredDescriptionDefault
endYes
fpsNo
startYes
styleNo
durationYes
overwriteNoExplicitly allow replacing existing media. Existing non-media files are protected.
output_pathYes

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

A3.5/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 behavioral burden. It discloses that the tool creates a standalone video and returns a dict with success status and output_path, but it omits important behavior such as overwrite handling, rendering cost, format details, and permission requirements.

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 front-loaded with the core purpose and then uses a compact Args/Returns structure. Every line adds practical information, and there is no filler.

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

Completeness4/5

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

Given a 7-parameter creation tool with no annotations and low schema description coverage, the description covers all required parameters and most optional ones. The output schema covers return details, and the overwrite parameter is partially covered by the schema, but the description still leaves some behavioral and usage context implicit.

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 description coverage is only 14%, so the description must compensate. It usefully documents six of the seven parameters: start, end, duration in seconds, absolute output_path, optional style keys, and fps default, though it does not mention the overwrite parameter.

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 states a specific verb and resource: generating an animated number counter video, and clarifies that it creates a standalone video of an animated counting number. This is clear enough to identify the tool, though it does not explicitly name or distinguish itself from sibling motion-graphics tools such as video_mograph_progress.

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?

The description explains what the tool produces but gives no guidance on when to use it versus alternatives, when not to use it, or any prerequisites. Usage is only implied by the purpose statement.

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