proofcut

Overview Schema Source Related Servers Discussions Admin

init

Idempotent

Create a new proofcut project folder, writing proofcut.json and empty assets, cache, media, and renders directories. It refuses to overwrite an existing project, so calling it is always safe.

Instructions

Create a proofcut project directory at path.

Writes proofcut.json and the empty assets/, cache/, media/ and renders/ directories, and nothing else — no media, no timeline. Refuses a directory that already holds a project rather than resetting it, so it is safe to call when unsure. Next is import_media, then a transcript, then seed_timeline.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	No	A name for the project, recorded in the manifest. Unset, the directory's own name is used.
`path`	No	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.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.25.0Sep 16, 2026

removedInput schema / properties / name / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / name / description

Added value: +"A name for the project, recorded in the manifest. Unset, the directory's own name is used."

removedInput schema / properties / name / title
```
Removed value: -"Name"
```

addedInput schema / properties / name / type

Added value: +[
+  "string",
+  "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 / title
```
Removed value: -"initArguments"
```

First observedv0.24.0Sep 15, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already mark it as idempotent and non-destructive, but the description adds crucial context: it writes only specific files and refuses to overwrite an existing project. This directly explains the idempotent behavior and gives the agent confidence about side effects. It also states what it does not do (no media, no timeline), which is valuable for setting expectations.

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 well-structured: the first sentence states the core action, the second details outputs and safety behavior, and the third gives the workflow sequence. It is concise with no redundant phrases, and the most important 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?

Given the tool's simplicity, the description covers the essential aspects: what it does, what it writes, what it refuses, and how to proceed next. The output schema exists to define the return value, so that is not a gap. The description also handles edge cases (bound vs unbound) clearly. Nothing an agent needs to call it correctly 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 both parameters are described in the schema. However, the description adds substantial meaning for the path parameter: how it resolves when bound to a project, relative path behavior, and refusal of external paths. This goes beyond the schema's basic description. The name parameter is not addressed in the description, but its schema description is adequate, so the added value is focused on the critical parameter.

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 clearly states the tool creates a proofcut project directory at a given path, specifies exactly what it writes (proofcut.json and four empty directories), and what it does not (media, timeline). It also positions itself as the first step before import_media and seed_timeline, differentiating it from sibling tools like migrate_project.

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 explicitly states when it is safe to call ('safe to call when unsure') because it refuses to reset an existing project, and provides a clear sequence of next steps: import_media, transcript, seed_timeline. It also gives detailed guidance on the path parameter, including bound-project behavior and refusal of paths outside the project, which helps an agent decide when and how to invoke it.

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

Deploy Server