Skip to main content
Glama
Files-com

Files.com MCP Server

Official
by Files-com

Gpg Decrypt File

Gpg_Decrypt_File

Decrypt a GPG-encrypted file and save the decrypted content to a specified destination path.

Instructions

Decrypt a GPG-encrypted file and save it to a destination path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoPath to operate on.
destinationNoDestination file path for the decrypted file.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations indicate non-read-only and non-destructive behavior. The description adds that it saves to a destination, but does not elaborate on side effects, permission requirements, or error conditions.

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?

Single sentence, no fluff, but could be expanded to include key prerequisites or a note about the source file.

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 an output schema present, the description is adequate for a simple decryption tool. However, it omits error conditions (e.g., missing key, file not found).

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%, with both 'path' and 'destination' parameters described. The tool description does not add meaning beyond what's in the schema.

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 clearly states the tool decrypts a GPG-encrypted file and saves it to a destination. This distinguishes it from siblings like Gpg_Encrypt_File and Unzip_File.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives, no prerequisites (e.g., GPG key availability), and no mention of the original file state after decryption.

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/Files-com/files-mcp'

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