Skip to main content
Glama

pdf_stamp

Stamp images, logos, or badges onto exact PDF page coordinates to add branding, approvals, or marks, then save the result as a new PDF.

Instructions

Stamp Image & Logo: Place coordinate-exact images, logos, and badges onto PDF pages. [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_stamp"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
outputYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, yet it says nothing about permissions, whether stamping is reversible, how the image and its position are conveyed, or what the resulting file looks like. Worse, it promises 'coordinate-exact' placement while the schema exposes only input and output paths, leaving the actual stamping mechanics unexplained. This is a meaningful gap for a mutation tool with zero annotation coverage.

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?

Two compact segments, front-loaded with the operation and its objects, with the input/output format tag appended. No filler sentences, though the bracketed format tag is boilerplate rather than genuinely informative given the tool's scope.

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 mutation tool with no annotations, no output schema, and 0% parameter documentation, the description leaves critical questions unanswered: how the image and its coordinates are specified, what happens to existing page content, and whether the output can overwrite the input. It is not complete enough for an agent to invoke the tool correctly beyond guessing.

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% for two required parameters, so the description must compensate. The only contribution is the '[Input: .pdf | Output: .pdf]' tag, which at least pins both parameters to PDF file paths, but nothing clarifies path conventions or where the image/coordinates would come from. The core semantics of the parameters remain undocumented.

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?

States a concrete verb ('Place') and resource ('images, logos, and badges onto PDF pages'), which is clearly distinct from siblings like pdf_annotate or pdf_extract_images. The 'Stamp Image & Logo' lead-in reinforces the operation type. It stops short of naming which sibling to use instead when the goal is text markup rather than image placement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites, and no routing to alternatives such as pdf_annotate for non-image overlays. The agent must infer the selection criteria entirely from the verb and the sibling names.

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