Skip to main content
Glama

Metis — Decrypt Backup

decrypt_backup

Decrypt .enc backup files to recover original .sqlite databases using the passphrase set during encryption.

Instructions

Decrypt a .enc backup produced by encrypt_backup().

Reverses the format [8B magic][16B salt][12B nonce][ciphertext+tag]. Writes the
recovered .sqlite next to the .enc file (dropping the .enc suffix) unless
output_path is given. The passphrase is never stored. This is the counterpart
to encrypt_backup — without it, encrypted backups could not be restored.

Args:
    enc_path:    Path to the .enc encrypted backup.
    passphrase:  The passphrase used at encryption time.
    output_path: Optional explicit destination for the decrypted file.

Returns JSON with out_path and the method used.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
enc_pathYes
passphraseYes
output_pathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

In the absence of annotations, the description adequately discloses key behaviors: output file location (next to .enc or explicit output_path), that the passphrase is never stored, the format reversal, and the return structure. It could mention potential overwrite behavior or error conditions, but what is provided is sufficient.

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 concise and well-organized: a one-sentence purpose, format details, output behavior, parameter listing, and return format. Every sentence adds value without redundancy.

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 presence of an output schema that likely details the return structure, the description adequately covers the tool's purpose, behavior, parameters, and output. It fully addresses the needs of a decryption tool in this context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage, so the description must compensate. It provides clear, informative descriptions for all three parameters (enc_path, passphrase, output_path), explaining their roles in the decryption process. This fully compensates for the lack of schema descriptions.

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 explicitly states that the tool decrypts a .enc backup produced by encrypt_backup(), and explains the format it reverses. It clearly distinguishes itself from the sibling encrypt_backup by being its counterpart.

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 identifies the tool as the counterpart to encrypt_backup, establishing when it should be used (to decrypt backups). While it doesn't explicitly list exclusion criteria, the context of being the decryption complement provides clear guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SVerITG/Metis'

If you have feedback or need assistance with the MCP directory API, please join our Discord server