Encryptor MCP

trash

Move a file or folder to the vault's recoverable deleted-items area, keeping it encrypted. Undo restores it; permanent deletion requires emptying and user approval.

Instructions

Put a file or folder in the vault's trash. It stays encrypted in the vault and can be taken back out with undo. Deleting for good is only possible by emptying the trash, which the user approves.

Input Schema

TableJSON Schema

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

Changed4 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 / 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.2/5.0

Behavior4/5

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

Annotations already declare destructiveHint=false, and the description adds meaningful context: items remain encrypted, are recoverable via undo, and permanent deletion requires a separate user-approved empty_trash. It does not mention vault-lock/auth prerequisites, which is the main remaining behavioral gap.

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 sentences with no waste. The core action is front-loaded, and the reversibility and permanence caveats follow in a natural order.

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?

With annotations, a full input schema, and an output schema, the description covers the essential behavioral profile for a trash operation. It could be improved by noting whether the vault must be unlocked, but it is otherwise complete for correct invocation.

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 all four parameters are already documented. The description adds no parameter-level detail beyond what the schema provides, making the baseline 3 appropriate.

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 (put in trash) and resource (file or folder in the vault), and explicitly distinguishes itself from permanent deletion and from undo. An agent can tell it apart from empty_trash and undo without opening any schema.

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?

Explains the intended use and contrasts it with permanent deletion via empty_trash, and notes recoverability through undo. It stops short of explicitly instructing when not to use it, but the sibling routing is clear enough for correct selection.

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

Deploy Server