Skip to main content
Glama
tydude001

proofcut

by tydude001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

check_frames

Read-onlyIdempotent

Check an export's frame count against the timeline's expected total, reporting the delta to verify cut positions before rendering without encoding.

Instructions

Check an export's frame count against what the timeline says it should be.

The picture-side counterpart to verify, which covers only the audio. Run this on the exported NLE project before rendering — that is where it is worth the most, because the count settles whether the cut positions are right for the price of reading a document rather than encoding one.

target is an NLE project (.kdenlive/.mlt/.xml, put to melt -consumer xml) or a finished render (counted with ffprobe). Omit it to just report expected_frames, the total the timeline lays down.

Read agrees first, then delta — how many frames the target has that the timeline does not. A non-zero delta on an NLE project means the render will not be the length the edit is, and notes says so when the cause is one proofcut already knows about. agrees is null, not false, for an audio-only render: it has no frames, so nothing was checked.

fps must match the rate the export ran at or the two sides are counting on different grids; it defaults to the rate export would have picked.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fpsNoThe rate the export ran at. It has to match, or the two sides are counting on different grids; it defaults to the rate `export` would have picked.
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.
targetNoAn NLE project (`.kdenlive`/`.mlt`/`.xml`) or a finished render. Omit it to just report `expected_frames`, the total the timeline lays down. Run it on the **exported project before rendering** — that is where it is worth the most.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv0.25.0
    • removedInput schema / properties / fps / anyOf
      Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / fps / description
      Added value: +"The rate the export ran at. It has to match, or the two sides are counting on different grids; it defaults to the rate `export` would have picked."
    • removedInput schema / properties / fps / title
      Removed value: -"Fps"
    • addedInput schema / properties / fps / type
      Added value: +[
+  "number",
+  "null"
+]
    • removedInput schema / properties / path / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / path / description
      Added value: +"The 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."
    • removedInput schema / properties / path / title
      Removed value: -"Path"
    • addedInput schema / properties / path / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedInput schema / properties / target / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / target / description
      Added value: +"An NLE project (`.kdenlive`/`.mlt`/`.xml`) or a finished render. Omit it to just report `expected_frames`, the total the timeline lays down. Run it on the **exported project before rendering** — that is where it is worth the most."
    • removedInput schema / properties / target / title
      Removed value: -"Target"
    • addedInput schema / properties / target / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedInput schema / title
      Removed value: -"check_framesArguments"
  2. First observedv0.24.0

TDQS

A4.9/5.0
Behavior5/5

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

Even though annotations already declare the tool read-only and idempotent, the description adds substantial behavioral context: how to read the output (`agrees` first, then `delta`), what a non-zero delta implies, that `agrees` is null rather than false for audio-only renders, and when `notes` will explain a mismatch. This goes beyond what the annotations provide and significantly helps the agent interpret results.

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 dense but every sentence earns its place: purpose, positioning relative to `verify`, best timing, target forms, output-field reading order, edge case, and fps caveat. The main purpose is front-loaded, and the length is appropriate for the tool's complexity.

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?

Given the annotations, full schema coverage, and the presence of an output schema, the description is complete. It covers the key behavioral edge cases an agent needs to call and interpret the tool correctly, and it names the relevant sibling alternative. Nothing essential appears 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 schema already documents all three parameters well. The description adds extra value by explaining the tooling for targets ('put to `melt -consumer xml`', 'counted with ffprobe') and reinforcing the `fps` matching constraint. It does not add much about `path`, but the schema's own description for `path` is already exhaustive.

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 and resource: 'Check an export's frame count against what the timeline says it should be.' It also distinguishes itself from the sibling `verify` by explicitly positioning itself as the picture-side counterpart. An agent can immediately tell what this tool does and how it differs from nearby tools.

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

Usage Guidelines5/5

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

The description gives clear when-to-use guidance: run it before rendering, and explains the target alternatives (NLE project vs finished render) and what omitting `target` does. It names the sibling `verify` as the audio-side alternative and says this tool covers the picture side. These explicit conditions leave little to inference.

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