Skip to main content
Glama

pdf_decrypt

Decrypt password-protected PDFs by supplying the user password and saving the unlocked document to a new output path.

Instructions

Decrypts a PDF using the provided password. [Input: PDF (.pdf) | Output: PDF (.pdf)]

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": {
      "input": "<input>",
      "password": "<password>",
      "output": "<output>"
    },
    "name": "pdf_decrypt"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesThe input PDF file path.
outputYesThe output PDF file path.
passwordYesThe user password.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It adds the input/output format convention, but says nothing about failure behavior on an incorrect password, whether the output is a new file or an overwrite, or what permissions the decrypted result retains — significant gaps for a security-relevant mutation.

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?

Two short sentences, front-loaded with the action and followed by a compact format tag. No wasted prose, though the format tag partly duplicates what the schema already conveys.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-parameter file operation with a fully documented schema and no output schema, the core contract is covered. The missing piece is error/edge-case behavior on wrong credentials, which matters for a decryption tool.

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 all three parameters (input, output, password) documented in the schema itself. The description adds no meaning beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ("Decrypts a PDF") plus the required credential, which cleanly separates it from the inverse pdf_encrypt operation. It stops short of naming a sibling or stating the boundary case explicitly, but the purpose is unambiguous.

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?

There is no when-to-use guidance beyond the implicit fact that the file must be encrypted and the password known. It doesn't mention what to do for non-encrypted inputs or how it relates to pdf_encrypt / pdf_change_permissions, leaving selection entirely to inference.

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