Skip to main content
Glama

PDF Watermark API - stamp text (DRAFT, CONFIDENTIAL) on pages

pdf_watermark
Read-onlyIdempotent

Put a diagonal or flat text watermark on all or chosen pages of a PDF, with size and opacity. Unicode text works. Runs on our server, files are deleted right after the call, nothing stored. Free: 25 calls/day per IP. Paid: $0.005 per call via x402 at https://radarbg.com/x402/pdf-watermark.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "DRAFT",
      "fileName": "sample.pdf",
      "fileContent": "JVBERi0xLjMKJeLjz9MKMSAwIG9iago8PAovUHJvZHVjZXIgKHB5cGRmKQo+PgplbmRvYmoKMiAwIG9iago8PAovVHlwZSAvUGFnZXMKL0NvdW50IDEKL0tpZHMgWyA0IDAgUiBdCj4+CmVuZG9iagozIDAgb2JqCjw8Ci9UeXBlIC9DYXRhbG9nCi9QYWdlcyAyIDAgUgo+PgplbmRvYmoKNCAwIG9iago8PAovVHlwZSAvUGFnZQovUmVzb3VyY2VzIDw8Cj4+Ci9NZWRpYUJveCBbIDAuMCAwLjAgNTk1IDg0MiBdCi9QYXJlbnQgMiAwIFIKPj4KZW5kb2JqCnhyZWYKMCA1CjAwMDAwMDAwMDAgNjU1MzUgZiAKMDAwMDAwMDAxNSAwMDAwMCBuIAowMDAwMDAwMDU0IDAwMDAwIG4gCjAwMDAwMDAxMTMgMDAwMDAgbiAKMDAwMDAwMDE2MiAwMDAwMCBuIAp0cmFpbGVyCjw8Ci9TaXplIDUKL1Jvb3QgMyAwIFIKL0luZm8gMSAwIFIKPj4Kc3RhcnR4cmVmCjI1NgolJUVPRgo="
    },
    "name": "pdf_watermark"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNol, m or sm
textYesWatermark text, e.g. CONFIDENTIAL
filesNoOr several files: [{fileName, fileContent (base64)}]
pagesNoPages, e.g. 1-3, 5, 8- (empty = all pages)
opacityNoStrength in percent: 20, 35 or 5535
fileNameNoFile name with extension, e.g. report.pdf
directionNodiag or flatdiag
fileContentNoThe file as base64 (a data: URI is fine)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent, and the description adds genuinely non-obvious behavior: server-side processing, immediate file deletion with nothing stored, a 25 calls/day free tier, and a $0.005 x402 paid path. It does not disclose how the watermarked file is returned (no output schema exists), which is the remaining behavioral gap.

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?

Three tight sentences: capability first, then support detail, then operational/pricing facts. The x402 URL is somewhat promotional but is actionable payment information, so it earns its place; minor density but no redundancy.

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 and no output schema, the definition should say what the caller gets back (base64 PDF, URL, or bytes) and how multi-file input affects the response. It covers cost, retention and Unicode well, but the return contract is left undefined for a tool that produces an artifact.

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%, including enum value hints for size, opacity and direction, so the baseline is 3. The description adds only one semantic detail beyond the schema — "Unicode text works" — plus the all-vs-chosen-pages distinction already conveyed by the `pages` description.

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 opens with a specific verb+resource ("Put a diagonal or flat text watermark ... on a PDF") and names the configurable dimensions (pages, size, opacity). The PDF resource implicitly separates it from image_watermark, but no sibling is named and no explicit routing statement is made.

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 only implied by the verb and the watermarking constraints; there is no statement of when to choose this over image_watermark or pdf_page_numbers, nor any when-not condition. The pricing/rate-limit sentences add operational context but not selection guidance.

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