Skip to main content
Glama

pdf_change_permissions

Configure user and owner permissions in a PDF to control printing, copying, and modification; specify input and output PDF files.

Instructions

Modify PDF Permissions: Configure user and owner permissions for printing, copying, and modification. [Input: .pdf | Output: .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>",
      "output": "<output>"
    },
    "name": "pdf_change_permissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
outputYes

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 must carry the behavioral burden; it discloses a PDF-to-PDF permission modification but little else. It does not explain password requirements, interaction with existing encryption, whether content is preserved, or whether the output is a new file rather than an in-place change.

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?

The description is brief, front-loads the operation, and includes a compact input/output convention. The opening phrase and following sentence are somewhat repetitive, and the compactness comes at the cost of important operational details.

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?

The definition is sufficient to recognize the general task but not to understand how a configurable permission change is requested. Given the absence of annotations, schema descriptions, permission parameters, and an output schema, the gaps around permission values and security behavior are substantial.

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?

The schema provides two undocumented string parameters, and the description usefully adds that input and output are PDF files. It does not clarify path or URI formats, and more importantly provides no way to understand how the promised printing, copying, modification, user, or owner permission settings are specified.

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 clearly states the action and resource: modifying PDF permissions, specifically user and owner permissions for printing, copying, and modification. It does not explicitly distinguish this operation from related siblings such as pdf_encrypt or pdf_decrypt.

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 permission categories imply that the tool should be used to change document usage restrictions. However, there is no explicit when-to-use or when-not-to-use guidance, prerequisite information, or routing to encryption or decryption alternatives.

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