Skip to main content
Glama

Add a watermark to a PDF

watermark_pdf
Idempotent

Add a text such as “CONFIDENTIAL” or “Copy for the bank” to every page of your PDFs, diagonally or repeated, in the colour and strength you want. Returns a link to download the result (kept about an hour). Credits on paid plans: 5 per file.

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

Input Schema

NameRequiredDescriptionDefault
textNoTextCONFIDENTIAL
colorNoColour Values: 'gris' = Grey; 'rojo' = Red; 'azul' = Bluegris
filesYesInput files (.pdf). Each one is a public http(s) URL, or an object with `url`, or with `name` and `content_base64` (small files only: up to 20 MB in total).
layoutNoLayout Values: 'diagonal' = Diagonal; 'horizontal' = Horizontal; 'mosaico' = Repeated across the pagediagonal
opacityNoStrength Values: 'suave' = Light; 'media' = Medium; 'fuerte' = Strongmedia

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, idempotentHint=true, non-destructive), and the description adds genuinely new context: the result is delivered as a download link that expires in about an hour, and the call consumes 5 credits per file on paid plans. It stops short of stating whether the source file is modified or a new file is produced, though the download-link wording implies the latter.

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?

Three tight sentences: the action and its variants first, then the return value and its lifetime, then cost. No padding, and the most decision-relevant information is front-loaded.

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 a 5-parameter tool with a fully documented schema and no output schema, the description covers the action, the result shape and lifetime, and the credit cost. Only the question of whether the original PDF is altered is left unstated, a minor gap given the non-destructive annotation and download-link framing.

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 100% and the enum values are already translated in the schema, so the schema does the heavy lifting. The description only loosely maps its wording to parameters ("diagonally or repeated" to layout, "colour and strength" to color and opacity) and adds no format or validation detail beyond that baseline.

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?

States a specific verb and resource (add a text watermark to every page of your PDFs) plus the visual variants (diagonal, repeated, colour, strength). An agent can immediately distinguish this from siblings like add_page_numbers or rotate_pdf without opening any schema.

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 clearly enough — you use it when you need to stamp text on PDF pages — and the credit cost hints at a paid workflow. However, no explicit when-not-to-use guidance, no prerequisites (e.g. input must be a valid PDF), and no named alternative for related stamping needs such as add_page_numbers.

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