Skip to main content
Glama

pdf_encrypt

Encrypt a PDF with a user password by specifying the input file, password, and output path, protecting sensitive documents with password-based access control.

Instructions

Encrypts a PDF with a user 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_encrypt"
  }
}

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?

With no annotations, the description carries the full behavioral burden and falls short: it does not state that this is a mutating operation requiring a writable output path, does not say whether owner permissions or encryption strength are configurable, and does not describe behavior on already-encrypted input. The '[Input: PDF | Output: PDF]' note is the only added context.

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, front-loaded elements: the action sentence followed by an input/output type tag. There is no wasted wording, though the bracketed format note is boilerplate rather than substantive.

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 transformation with fully documented schema, the definition covers the essentials of what it does and the file types involved. It omits the behavioral details an agent would want for an encryption/mutation tool, such as overwrite behavior and error cases on encrypted input.

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 100%, so all three parameters (input, password, output) are already documented in the schema. The description adds only that the password is a 'user password', a minor clarification beyond the schema; 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 ('Encrypts a PDF') and the key modifier ('with a user password'), so the operation is unambiguous. It does not explicitly distinguish itself from the sibling pdf_decrypt, but the name and verb do that implicitly.

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 guidance on when to use this versus pdf_decrypt or pdf_change_permissions, no prerequisites, and no note about what happens if the input is already encrypted. The agent is left to infer usage entirely.

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