PatchWarden

sync_file

Destructive

Copy a file from source to target within the same Direct session repo, with optional SHA256 verification to ensure file integrity.

Instructions

Copy a file from source to target within the same Direct session repo. This legacy operation is outside the first Direct review MVP and is disabled when directReview.mode=enforce. Both paths must be inside the session repo_path.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_id": "<session_id>",
      "source_path": "<source_path>",
      "target_path": "<target_path>"
    },
    "name": "sync_file"
  }
}

Input Schema

Name	Required	Description
`session_id`	Yes	Direct session ID
`source_path`	Yes	Relative path to source file within repo
`target_path`	Yes	Relative path to target file within repo
`expected_source_sha256`	No	Optional: expected sha256 of source file
`expected_target_sha256`	No	Optional: expected sha256 of target file before copy

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.0Jul 8, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds context about it being a legacy operation and a path constraint, providing some value beyond annotations. However, it does not elaborate on overwrite behavior or return values, so it is adequate but not rich.

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, each serving a purpose: stating the action, flagging legacy/disabled status, and constraining paths. No filler or redundancy.

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

Completeness4/5

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

For a simple file copy operation with full schema coverage and annotations, the description provides adequate context: clear purpose, key constraints, and availability caveat. It does not mention return values, but the lack of an output schema lowers the burden, and the tool's simplicity makes this acceptable.

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%, so the schema already documents all parameters. The description reinforces that paths are relative to the repo but does not add new semantic details beyond the schema, earning the baseline score.

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+resource: 'Copy a file from source to target within the same Direct session repo.' This clearly identifies the tool's function and distinguishes it from siblings like move_file and delete_file. The added context about it being a legacy operation further clarifies its unique role.

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

Usage Guidelines4/5

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

The description states when not to use the tool (disabled when directReview.mode=enforce) and a hard constraint (both paths must be inside the session repo_path). It provides clear usage context but does not explicitly name an alternative tool, so it stops short of a full 5.

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

Deploy Server