proofcut

Overview Schema Source Related Servers Discussions Admin

pack_apply_captions

DestructiveIdempotent

Apply a caption preset from the active pack variant to the project, using resolved settings so later pack swaps won't change the style. Use this to restyle captions without reapplying the pack.

Instructions

Apply the active pack variant's caption preset, through caption_style.

Concrete resolved fields, never a live pointer: this reads the preset's already-resolved dict off the snapshot and hands it to the ordinary caption_style call, so a later pack swap can never silently overwrite a project's caption look out from under it. Separate from pack_apply on purpose — applying a pack never restyles captions on its own, only this does.

Input Schema

TableJSON Schema

Name	Required	Description
`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.
`plan`	No	Resolve the whole call and report what it would do, writing nothing. Prefer it over doing the thing and undoing it.
`preset`	Yes	Which caption preset of the active variant to apply, through the ordinary `caption_style` call. This is the only thing that restyles captions from a pack; `pack_apply` never does it on its own.

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 / 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"
+]

addedInput schema / properties / plan / description

Added value: +"Resolve the whole call and report what it would do, writing nothing. Prefer it over doing the thing and undoing it."

removedInput schema / properties / plan / title
```
Removed value: -"Plan"
```

addedInput schema / properties / preset / description

Added value: +"Which caption preset of the active variant to apply, through the ordinary `caption_style` call. This is the only thing that restyles captions from a pack; `pack_apply` never does it on its own."

removedInput schema / properties / preset / title
```
Removed value: -"Preset"
```

removedInput schema / title

Removed value: -"pack_apply_captionsArguments"

First observedv0.24.0Sep 15, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already indicate destructive and idempotent behavior, and the description adds meaningful behavioral context: it reads already-resolved fields from a snapshot rather than a live pointer, so a later pack swap cannot silently overwrite the project's caption look. This is the kind of implementation-level guarantee that an agent cannot infer from the schema alone.

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 compact and front-loaded: the first sentence states the action, and the second paragraph earns its place by clarifying the snapshot behavior and the relationship to pack_apply. Every sentence adds distinct value.

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 rich input schema, output schema, and annotations, the description covers the key contextual facts an agent needs: what gets applied, how it is resolved, why it is separate from pack_apply, and what makes it safe against later pack swaps. Nothing necessary for correct invocation is missing.

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 100%, and the tool description does not add parameter-specific meaning beyond what the schema already provides. The description mentions 'caption preset' and 'caption_style', but the preset parameter already says the same thing; the baseline of 3 is appropriate.

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 uses a specific verb ('Apply'), names the exact resource ('the active pack variant's caption preset'), and clarifies the mechanism ('through caption_style'). It explicitly separates itself from pack_apply, so an agent can immediately distinguish this tool from its siblings.

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 explicit when-not guidance: 'Separate from pack_apply on purpose — applying a pack never restyles captions on its own, only this does.' This directly tells the agent that pack_apply is not the way to restyle captions and that this tool is the intended route.

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

Deploy Server