Skip to main content
Glama
Sign In

PDFOven

by com.pdfoven
OverviewDiscussionsAdmin

Watermark PDF

watermark_pdf
Idempotent

Stamp text (Latin characters) or a PNG/JPEG image onto a PDF's pages: centred and diagonal, tiled, or in a corner. Uses one render.

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": {
      "file": "<file>"
    },
    "name": "watermark_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesThe PDF to watermark.
textNoWatermark text, up to 5 lines.
colorNoHex text color, e.g. #c8155f.
imageNoPNG or JPEG image instead of text.
pagesNoPages like "1-3,5,8-" or "last". Ranges can run backwards ("last-1") to reverse order.
opacityNo
positionNo
rotationNoDegrees. Defaults to the page diagonal for center and tile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare non-destructive, idempotent, open-world behavior, so the bar is lower. The description adds the Latin-character limitation and the phrase 'Uses one render' — presumably a credit/quota cost — but that is cryptic, and it never states that a new watermarked PDF is produced or under what handle it is returned.

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 short sentences, front-loaded with the resource and the input variants, with zero filler. Nothing is restated from the schema unnecessarily.

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

Completeness3/5

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

With 8 parameters, nested file/image objects, and no output schema, the description should say what comes back (a new PDF, its location/encoding) and that the source is untouched. Neither is covered, leaving a real gap for an agent that must act on the result.

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 coverage is 75%, so the baseline is 3. The description adds the meaningful constraint that only Latin characters are supported for text, but it does not clarify the text/image exclusivity, opacity interaction with color, or how position and rotation combine.

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?

Specific verb ('stamp') plus resource ('PDF's pages') with the two supported media (text, PNG/JPEG) and the layout modes named. No sibling in the list does watermarking, so an agent can pick this immediately over compress_pdf or render_pdf.

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?

Usage is implied by the name and the first clause, but there is no explicit when-to-use/when-not guidance, no mention that text and image are mutually exclusive, and no routing to alternatives. The agent has to infer context from the tool name alone.

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

All PDFOven toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources