Skip to main content
Glama

pdf-suite

pdf_unlock_strip_restrictions

Load owner-restricted PDFs (ignoreEncryption) and re-serialize clean unlocked pages without permission locks.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pdf_unlock_strip_restrictions"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputPathNo
base64DataNo
outputPathNo

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 behavioral burden. It does disclose the ignoreEncryption behavior and that pages are re-serialized without permission locks, but it omits whether a password is ever required, whether signatures or metadata are invalidated, whether the source file is modified, and what happens on failure.

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?

A single dense sentence with the key behavior front-loaded and no filler. It is compact, though the parenthetical '(ignoreEncryption)' is the only nod to the underlying parameters.

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

Completeness2/5

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

For a mutation tool with no annotations, no output schema, and three entirely undocumented parameters, the description is too thin. An agent cannot determine how to supply input, where output lands, or what the tool returns.

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

Parameters2/5

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

Schema description coverage is 0% across three parameters, and the description never mentions inputPath, base64Data, or outputPath. It gives no hint that input can be supplied either as a path or as base64 data, nor where the unlocked result is written, so it fails to compensate for the schema gap.

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?

States a specific verb and resource: loading owner-restricted PDFs and re-serializing them without permission locks. It is clearly distinct from siblings like pdf_protect_metadata, though it never names an alternative explicitly.

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

Usage Guidelines3/5

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

The phrase 'owner-restricted PDFs' implies the condition for use, but there is no explicit when-to-use/when-not guidance, no mention of what to do for user-password-protected files, and no named alternative among the many sibling PDF tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources