Skip to main content
Glama

pdf_overlay_underlay

Apply letterheads, watermarked stationery, or templates as background or foreground layers to PDFs, producing an updated PDF for branded or protected documents.

Instructions

Overlay & Underlay Stationary: Apply letterheads, watermarked stationary, and templates as background or foreground. [Input: .pdf | Output: .pdf]

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": {
      "input": "<input>",
      "output": "<output>"
    },
    "name": "pdf_overlay_underlay"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
outputYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the input and output formats (.pdf), but does not state overwrite behavior, permissions, page-size matching requirements, or error handling for a file-mutating operation. This leaves key behavioral traits undisclosed.

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?

The description is front-loaded and compact, with no unnecessary sentences. The bracketed input/output format adds useful structure. Minor typographical awkwardness ('Stationary') and the missing role clarification keep it from being fully polished.

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 PDF file-mutation tool with no annotations, no output schema, and 0% schema description coverage, the description is too thin. It does not explain how the overlay source is provided, how pages are aligned, or what the output contains, leaving an agent without enough information to invoke the tool correctly.

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%, and the description only supplies file format hints for the two parameters. It does not clarify which parameter is the base PDF, which is the overlay/template, or how the letterhead/stationery file is identified. The critical parameter roles remain 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 uses a specific verb ('Apply') and names concrete resources: letterheads, watermarked stationary, and templates, applied as background or foreground. This clearly identifies the overlay/underlay operation. It stops short of a 5 because it does not clarify the input file roles, which is essential to understanding how the letterhead/template is supplied.

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?

The stated use cases (letterheads, watermarked stationary, templates) imply when an agent should choose this tool. However, there is no explicit when-to-use or when-not-to-use guidance, and no alternatives are named. Usage is inferable but not directly defined.

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