Skip to main content
Glama

Add page numbers or a watermark

stamp_pdf

Number the pages, stamp a text watermark on every page, or both in one go. Page number format uses %d twice, e.g. "Page %d of %d".

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": "stamp_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNoA file the person attached in ChatGPT (filled in by ChatGPT).
file_idNoA FynePDF file_id from upload_file, import_file_from_url or an earlier tool.
file_urlNoA public link to the file.
watermarkNo
page_numbersNo
library_file_idNoA file from the person's FynePDF Library (from list_library_files).

Output Schema

NameRequiredDescriptionDefault
cardNo
filesYes
stepsYes
job_idYes
statusYes
creditsYes
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changed
    • removedOutput schema / properties / files / items / properties / bytes / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / files / items / properties / bytes / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / files / items / properties / download_url / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / files / items / properties / download_url / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / files / items / properties / pages / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / files / items / properties / pages / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / steps / items / properties / bytes_after / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / steps / items / properties / bytes_after / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / steps / items / properties / bytes_before / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / steps / items / properties / bytes_before / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / steps / items / properties / pages_after / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / steps / items / properties / pages_after / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / steps / items / properties / pages_before / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / steps / items / properties / pages_before / type
      Added value: +[
      +  "number",
      +  "null"
      +]
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false, so the safety profile is covered. The description adds that numbering and watermarking can be combined per call, but says nothing about result handling — whether a new file/file_id is returned, whether the source is modified in place, or whether repeated calls stack stamps (relevant given idempotentHint=false).

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 with the operation set front-loaded and the format syntax second; nothing is wasted and there is no preamble.

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?

For a tool with 6 parameters, nested objects, and four alternative file references (file, file_id, file_url, library_file_id) and zero required parameters, the description never explains which file source to provide or how they interact — a significant inference left to the agent. An output schema exists so return values need not be described, which limits the damage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description supplies meaning the schema does not: the page-number format placeholder must be %d used twice, with a concrete example "Page %d of %d". That is exactly the kind of non-obvious semantic detail the schema's bare maxLength=60 string leaves out. Remaining gaps are minor since watermark fields (size, color, opacity, rotation) and page_numbers fields are largely self-documenting from their names and constraints, and the file-source parameters carry their own schema descriptions.

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 set and resource: number pages, stamp a text watermark, or both. No sibling tool (protect_pdf, redact_pdf, edit_pages, sign_pdf) does stamping, so an agent can select this unambiguously.

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?

"or both in one go" tells the agent the two operations are composable in a single call, which is useful selection guidance. However there is no when-not guidance, no prerequisite (a file must first be uploaded/imported), and no pointer to upload_file/import_file_from_url as the source-producing siblings.

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.