proofcut

Overview Schema Source Related Servers Discussions Admin

pack_status

Read-onlyIdempotent

Check the active pack variant and flag stale cards or caption presets that drifted from it, identifying which need reauthoring to sync with the current variant.

Instructions

Active pack variant, and which cards/captions have drifted from it.

A card is stale when its own recorded pack_hash no longer matches the active variant's current hash — not wrong, since card_new only pre-merges a pack's style and a per-call slot still wins, but worth a card_reauthor to catch up. caption_preset_stale is the same question for whatever pack_apply_captions last wrote.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`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.

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

removedInput schema / title
```
Removed value: -"pack_statusArguments"
```

First observedv0.24.0Sep 15, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds valuable interpretation beyond those flags: 'stale' does not mean wrong, a per-call slot still wins, and caption_preset_stale tracks the last pack_apply_captions write. This gives the agent accurate expectations about what the status values mean and what action they imply.

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 three sentences with the core statement front-loaded and two dense but purposeful sentences explaining the stale semantics. Nothing is redundant, and the technical nuance earns its place.

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?

For a read-only status tool with a full output schema and safety annotations, the description is complete: it defines the two drift statuses, explains why stale is not wrong, and points to the relevant follow-up tool. The only implicit notion, 'active pack variant,' is a consistent domain term supported by sibling tools like pack_activate.

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?

The only parameter, path, is fully documented in the input schema with 100% coverage, including its optional behavior when bound to a project. The description contains no parameter-level detail, which is acceptable because the schema already carries that burden.

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 names the resource ('active pack variant') and the specific output (which cards/captions have drifted), so an agent can tell what the tool reports. It lacks an explicit verb, but the status framing and concrete drift/stale terminology make the purpose clear and distinguishable from pack_show.

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

Usage Guidelines3/5

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

The description implies usage context: when a card's recorded pack_hash no longer matches the active variant, a card_reauthor may be worth doing, and caption_preset_stale refers to what pack_apply_captions last wrote. However, it never explicitly states when to call pack_status versus a sibling like pack_show or pack_apply, so the guidance is implied rather than explicit.

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

Deploy Server