Encryptor MCP

copy_file

Duplicate a file to a new name or folder inside the same vault while keeping the copy encrypted throughout the operation.

Instructions

Copy a file to a new name or folder in the same vault (stays encrypted the whole time).

Input Schema

TableJSON Schema

Name	Required	Description
`to`	Yes	The path for the copy in the same vault, for example 'Taxes/receipts copy.md'. It must be free.
`path`	Yes	A path inside the vault, from its top, for example 'Taxes/2025/receipts.md'.
`vault`	Yes	The vault's name, as listed by the vaults tool, for example 'Taxes'.
`purpose`	Yes	A few words on why, shown to the user or kept in the vault's change log.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.1.4Oct 21, 2026

addedInput schema / properties / path / description

Added value: +"A path inside the vault, from its top, for example 'Taxes/2025/receipts.md'."

addedInput schema / properties / purpose / description

Added value: +"A few words on why, shown to the user or kept in the vault's change log."

addedInput schema / properties / to / description

Added value: +"The path for the copy in the same vault, for example 'Taxes/receipts copy.md'. It must be free."

addedInput schema / properties / vault / description

Added value: +"The vault's name, as listed by the vaults tool, for example 'Taxes'."

First observedv0.1.3Oct 20, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), and the description adds genuinely new context: the copy stays encrypted throughout. It still omits what happens when the destination is occupied or whether the copy is undoable, but the encryption guarantee is real added value beyond structured fields.

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?

A single front-loaded sentence with the core action first and the scoping constraint immediately after. The parenthetical about encryption earns its space; nothing is padded.

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?

An output schema exists, so return values need no explanation, and the schema covers all four parameters thoroughly. The description supplies purpose and the encryption/same-vault constraints, leaving only failure modes (destination exists, permissions) unstated.

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 all four parameters are documented in the schema, including the 'must be free' constraint on 'to'. The description adds no parameter-level detail, so the baseline of 3 applies.

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?

States a specific verb and resource ('Copy a file') plus the destination scope ('to a new name or folder in the same vault'). The copy-vs-move distinction is implied by the verb and the same-vault constraint, but the sibling 'move' tool is never named, so an agent must infer the routing itself.

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?

Usage is only implied: 'in the same vault' tells the agent this is an intra-vault operation and hints that cross-vault copies need something else, but there is no explicit when-to-use, no prerequisites, and no named alternative versus 'move' or 'write_file'.

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

Deploy Server