Skip to main content
Glama

protect_pdf

Encrypt a PDF with AES-256 and a password so it cannot be opened without it. Use it to protect private documents before sharing.

Instructions

Encrypt a PDF with AES-256 so it cannot be opened without the password. Use this before sending a document that contains anything private. The input is uploaded to the Papyrio API, processed in memory and not stored. The result is written to output_path, replacing any file already there, and the call returns that path and the size in bytes. Inputs are limited to 50 MB, and each call counts as one operation against the daily quota.

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": {
      "file": "<file>",
      "password": "<password>"
    },
    "name": "protect_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesAbsolute path to the PDF to encrypt.
passwordYesPassword that will be required to open the resulting PDF.
output_pathNoAbsolute path to write the result to. Defaults to the input file with a "-papyrio.pdf" suffix.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it says the input is uploaded to the Papyrio API, processed in memory and not stored, that output_path is overwritten (a destructive side effect the schema does not flag), the return value shape, the 50 MB input limit, and per-call quota consumption.

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?

Four sentences, each carrying distinct new information (purpose, trigger, data handling, side effects/limits), with the core action stated first and zero filler.

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?

No output schema exists, so the description supplies the return value itself, and it covers the destructive overwrite, privacy handling, size cap, and quota. For a 3-parameter encryption tool this is complete enough to call correctly without guessing.

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

Parameters4/5

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

Schema description coverage is 100%, so a baseline of 3 is warranted, but the description adds real meaning beyond the schema by disclosing that output_path replaces any existing file and that the call returns the path and byte size. It doesn't discuss password strength requirements, a minor omission.

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?

States a specific verb and resource ('Encrypt a PDF with AES-256') along with the concrete effect: the file cannot be opened without a password. This is instantly distinguishable from sibling tools such as unlock_pdf or compress_pdf.

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?

Gives a clear usage trigger: 'Use this before sending a document that contains anything private.' That tells an agent when to reach for it, though it never names unlock_pdf or other alternatives as the opposite operation, so the alternative framing is only implicit.

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