Skip to main content
Glama
PurpleDirective

quillpdf-mcp

by PurpleDirective
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Watermark a PDF

pdf_watermark

Stamp a text watermark on every page of a PDF, with control over color, opacity, size, and placement. Files are processed locally and never uploaded.

Instructions

Stamp a text watermark on every page. Runs entirely on this machine — the file is read and written locally and never sent anywhere.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesWatermark text
colorNoColor as #RRGGBB (default #808080)
forceNoReplace the output file if it already exists (default: refuse, so existing files are never silently clobbered)
inputYesPath to the input PDF
outputYesPath to write the watermarked PDF
opacityNoOpacity 0-1 (default 0.15)
fontSizeNoFont size in points (default 48)
positionNoPlacement (default center)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • addedInput schema / properties / force
      Added value: +{
+  "description": "Replace the output file if it already exists (default: refuse, so existing files are never silently clobbered)",
+  "type": "boolean"
+}
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations declare readOnly=false, idempotent=false, destructive=false, and the description meaningfully adds that processing is local — the file is read and written on this machine and never sent anywhere. That privacy/execution-model detail is genuine context beyond the annotations, though it says nothing about overwrite behavior (left to the force param).

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?

Two tight sentences with the operation stated first and the execution/privacy note second. No filler or redundancy.

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 an 8-parameter local file tool with fully documented schema and no output schema, the description covers purpose and the non-obvious privacy behavior. Overwrite semantics are handled by the schema's force description, so remaining gaps are minor.

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 schema already documents all eight parameters including force, opacity, fontSize, and the position enum. The description adds no parameter detail, so the 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 — 'Stamp a text watermark on every page' — and the 'every page' scope tells the agent the extent of the operation. It is clearly a watermarking tool distinct in intent from sibling text-overlay tools like pdf_bates or pdf_page_numbers, but it never names or contrasts a sibling explicitly.

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 when-to-use guidance, no prerequisites, and no alternatives named. The privacy sentence ('Runs entirely on this machine') is context about processing location, not guidance on when to select this tool over pdf_bates or pdf_page_numbers.

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