CodeRecoder MCP

Overview Schema Source Related Servers Discussions Admin

Create Verified Code Backup

create_project_snapshot

Create a restorable, SHA-256-verified backup of the active project, with optional deduplication of unchanged files for efficient storage.

Instructions

Create an independently restorable, SHA-256-verified backup of the active project. Unchanged files may be deduplicated in storage.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No
`tags`	No
`prompt`	No
`skipIfUnchanged`	No	Defaults to false for explicit backups

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`error`	No
`message`	Yes
`success`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed17 schema fields changedv3.1.0Sep 11, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

removedInput schema / properties / name / description

Removed value: -"Optional user-friendly name for the snapshot (e.g., \"Feature Complete\", \"Before Refactor\")"

addedInput schema / properties / name / maxLength
```
Added value: +200
```
addedInput schema / properties / name / minLength
```
Added value: +1
```
removedInput schema / properties / name / optional
```
Removed value: -true
```

removedInput schema / properties / projectPath

Removed value: -{
-  "description": "Optional project path. Uses current active project if not provided.",
-  "optional": true,
-  "type": "string"
-}

removedInput schema / properties / prompt / description

Removed value: -"Description of changes being saved"

addedInput schema / properties / prompt / maxLength
```
Added value: +2000
```
addedInput schema / properties / prompt / minLength
```
Added value: +1
```

addedInput schema / properties / skipIfUnchanged

Added value: +{
+  "description": "Defaults to false for explicit backups",
+  "type": "boolean"
+}

removedInput schema / properties / tags / description

Removed value: -"Optional tags for categorizing snapshots (e.g., [\"stable\", \"feature\"])"

addedInput schema / properties / tags / items / maxLength
```
Added value: +80
```
addedInput schema / properties / tags / items / minLength
```
Added value: +1
```
addedInput schema / properties / tags / maxItems
```
Added value: +32
```
removedInput schema / properties / tags / optional
```
Removed value: -true
```
removedInput schema / required
```
Removed value: -[
-  "prompt"
-]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "additionalProperties": {},
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "error": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "message"
+  ],
+  "type": "object"
+}

First observedv1.1.0Aug 10, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the safety profile is established. The description adds valuable context beyond annotations: the backup is 'independently restorable' and 'SHA-256-verified,' and that 'unchanged files may be deduplicated in storage.' This clarifies reliability and storage behavior. It doesn't contradict the annotations.

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?

Two concise sentences, front-loading the core purpose and then adding behavioral context. No wasted words; every sentence earns its place.

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

Completeness3/5

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

The tool has hidden complexity (4 parameters, no required fields, a nested-free schema, and an output schema that likely details the backup metadata). The description covers purpose and some behavioral traits but omits parameter usage and does not mention the output schema's role. Given the sibling context, it could better guide the agent on when to call this versus others. Adequate but incomplete.

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?

With four parameters and only 25% schema description coverage (only skipIfUnchanged has a description), the description does not compensate for the missing parameter documentation. It does not explain what 'name', 'tags', or 'prompt' mean or how they affect the snapshot, nor does it clarify the default behavior of skipIfUnchanged beyond what the schema already says. Baseline 3 for low coverage when no additional meaning is provided.

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?

States a specific verb (create), resource (project snapshot/backup), and distinguishes this tool from siblings by emphasizing 'independently restorable' and 'SHA-256-verified' – qualities not implied by verify_project_snapshot or list_project_snapshots. The description clearly signals it is a mutating creation operation and not a read or verification tool.

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 ('create a backup of the active project') but provides no explicit when-to-use vs when-not-to-use guidance. It does not explain which sibling tools to prefer (e.g., list_project_snapshots to inspect existing backups first) or when a snapshot is unnecessary. For a tool with eight siblings, this is a missed opportunity to route the agent.

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

Deploy Server