Encryptor MCP

move

Relocate or rename a file or folder within one vault without overwriting data; the new path must be free.

Instructions

Move or rename a file or folder, within one vault. Nothing is overwritten: the new place must be free.

Input Schema

TableJSON Schema

Name	Required	Description
`to`	Yes	The new path in the same vault, for example 'Archive/2025/notes.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'.
`confirm`	No	Leave empty. Only pass the code a previous answer gave you, after the user agreed.
`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.

Changed5 schema fields changedv0.1.4Oct 21, 2026

addedInput schema / properties / confirm / description

Added value: +"Leave empty. Only pass the code a previous answer gave you, after the user agreed."

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 new path in the same vault, for example 'Archive/2025/notes.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

A4.3/5.0

Behavior4/5

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

Although annotations cover the safety profile, the description adds vital behavioral context by explicitly stating 'Nothing is overwritten.' This proactive assurance significantly reduces the risk profile and informs the agent about the atomicity of the move operation.

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 definition is highly concise. It front-loads the core action and uses the single sentence structure to deliver the primary function and the most critical behavioral constraint without unnecessary phrasing.

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?

With 100% schema coverage, the addition of the behavioral guarantee ('Nothing is overwritten') provides the necessary high-level operational completeness required for the agent to use the tool safely and correctly.

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?

Since schema description coverage is 100%, the description's primary function is reinforcement. The sentence about the new place needing to be free reiterates a condition already defined in the `to` parameter schema, making it adequate but not adding new semantic meaning.

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 clear verbs ('Move or rename') and identifies the resource ('file or folder'). It successfully distinguishes its function from other siblings by defining its scope as confined 'within one vault'.

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?

It clearly states a critical operational constraint: 'Nothing is overwritten: the new place must be free.' This acts as a crucial guideline on when the tool is expected to succeed or fail, directing the agent's input parameters.

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

Deploy Server