Encryptor MCP

unlock

Open a locked Cryptomator vault for AI file access while the user enters the password locally, never in chat, and sets how long it stays open.

Instructions

Ask the user to open a locked vault. The user types the password on their own computer (a local page or a password box), never in this chat, and chooses how long it stays open. purpose: a few words on why, shown to the user. Never ask the user for the password yourself.

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": {
      "vault": "<vault>",
      "purpose": "<purpose>"
    },
    "name": "unlock"
  }
}

Input Schema

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

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.1.4Oct 21, 2026

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.4/5.0

Behavior5/5

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

The description discloses critical behavior beyond the annotations: the user types the password locally, never in chat, chooses the unlock duration, and sees the purpose. This is exactly the kind of security-sensitive interaction detail an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded and appropriately sized. The final sentence reinforces the security-critical warning, though it repeats the earlier 'never in this chat' point.

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?

Given the two required parameters and the presence of an output schema, the description is complete. It covers the interaction model, password handling, and user-facing purpose without needing to explain return values.

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 both parameters are already well documented. The description adds only marginal meaning, such as the purpose being shown to the user, but largely repeats what the schema provides.

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 a specific verb and resource: asking the user to open a locked vault. It clearly distinguishes this from a direct unlock operation by explaining the user interaction model, so an agent can tell it apart from sibling tools like lock.

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 implies usage when a vault is locked and gives a strong directive: never ask the user for the password yourself. It does not explicitly name alternatives or exclusions, but the context is sufficient 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