Skip to main content
Glama

decrypt_backup

Decrypt .enc backup files using the original passphrase to restore the SQLite database. Specify the encrypted file path and passphrase; optionally set an output path.

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
Behavior5/5

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

No annotations provided, so description carries full burden. It discloses file format, output location (next to .enc with .sqlite), passphrase security (never stored), and return format (JSON with out_path and method). This is thorough and honest about behavior.

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?

Description is front-loaded with purpose and technical details, followed by structured Args list and return info. Every sentence adds value, no redundancy, and is appropriately sized for the tool's complexity.

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?

Covers core functionality, file format, output behavior, and return type. Given the presence of an output schema, return values are presumably documented. Missing error handling or edge cases, but overall complete for typical usage.

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 coverage is 0%, so description must compensate. It lists three parameters with brief explanations (path, passphrase, optional destination). This adds meaning beyond the schema, but lacks details on validation or error conditions. Adequate but not rich.

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?

Description clearly states 'Decrypt a .enc backup' and specifies the file format and output behavior. It distinguishes itself as the counterpart to encrypt_backup, making its purpose unambiguous and differentiated from sibling tools.

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?

Description implies use after encrypt_backup and mentions passphrase requirement, but lacks explicit when-not-to-use guidance or alternatives (e.g., verify_backup for integrity checks). Context is clear but not exhaustive.

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