Skip to main content
Glama
Sign In
pdf-toolkit-mcp

pdf-toolkit-mcp

by EigenCharlie
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

unlock_pdf

Remove password protection from a PDF file by providing the correct password, then save the unprotected PDF to disk.

Instructions

Remove password protection from a PDF. Requires the correct password. Produces an unprotected .pdf file on disk.

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_file": "<input_file>",
      "password": "<password>"
    },
    "name": "unlock_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
passwordYesThe password to unlock the PDF. Handled as a secret and sent only to iLoveAPI.
input_fileYesPath to the password-protected PDF file.
output_pathNoOptional output path. If it ends with the expected extension, the file is written there. If it is a directory, the file is placed inside with a timestamped name. Defaults to the same directory as the first input.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description must cover behavioral traits. It states the tool 'removes password protection' and 'produces an unprotected .pdf file on disk,' but omits details like password security handling (though the schema mentions it), error behavior on wrong password, or whether the original file is modified. This is adequate but minimal.

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?

The description is two short sentences with no unnecessary words. It front-loads the key action and ends with the output behavior. Every sentence contributes meaningful information.

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?

For a simple tool with 3 parameters and no output schema, the description explains the input requirement and output file. The schema provides detailed parameter descriptions. The description omits potential error conditions or return values, but overall it is complete enough for the tool's simplicity.

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%, so the description adds no extra parameter meaning beyond what the schema already provides. The baseline score of 3 is appropriate.

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 explicitly states the action: 'Remove password protection from a PDF.' It clearly distinguishes this tool from siblings like 'protect_pdf' (which adds protection) and other PDF operations. The verb 'remove' and resource 'PDF' are specific.

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?

The description notes the prerequisite 'Requires the correct password,' which implies when to use: when you have the password. It does not explicitly mention when not to use or alternatives, but the context of sibling tools makes the usage clear.

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

Deploy Server

Other Tools