Skip to main content
Glama

pdf-suite

pdf_add_watermark

Overlay a diagonal translucent vector text watermark (e.g. CONFIDENTIAL) across all pages of a PDF.

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_add_watermark"
  }
}

Input Schema

NameRequiredDescriptionDefault
opacityNo
inputPathNo
base64DataNo
outputPathNo
watermarkTextNoCONFIDENTIAL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It usefully discloses the watermark's visual traits (diagonal, translucent, vector, applied to all pages), but says nothing about whether the source PDF is modified in place or written to outputPath, whether an existing watermark is replaced, or any permission/size constraints for a mutation operation.

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?

A single front-loaded sentence with no filler; the verb and the visual scope come first and the parenthetical example adds practical value rather than waste.

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 five-parameter mutation tool with no annotations, no output schema, and no schema descriptions, the definition is too thin: the choice between inputPath and base64Data, where results land, and whether the original file is altered are all left unstated.

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 five parameters. The description hints at only two of them ('translucent' for opacity, the example text for watermarkText) and leaves inputPath, base64Data, outputPath, and the defaults completely unexplained, so the input/output routing is ambiguous.

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 gives a specific verb ('Overlay') and resource ('diagonal translucent vector text watermark ... across all pages of a PDF'), plus a concrete example (CONFIDENTIAL). It implicitly separates itself from siblings like pdf_add_page_numbers or pdf_redact_terms by naming the visual style, 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 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 mention of when a different tool (e.g. redaction or page numbering) would be preferred. The agent must infer applicability entirely from the purpose sentence.

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