Skip to main content
Glama

pdf_header_footer

Add custom header or footer text to a PDF at the top or bottom, saving the result to a new file.

Instructions

Adds a header or footer to a PDF. [Input: PDF (.pdf) | Output: PDF (.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>",
      "text": "<text>",
      "position": "<position>"
    },
    "name": "pdf_header_footer"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to add.
inputYesThe input PDF file path.
outputYesThe output PDF file path.
positionYese.g. 'top' or 'bottom'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/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 behavioral burden, yet it discloses almost nothing: not whether the header applies to all pages or a subset, not whether the source file is modified or a new file written, not how conflicts with existing content are handled, and not what formatting control exists over the text. Only the generic Input/Output format tag is added.

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 compact clauses with the purpose front-loaded and the format signature bracketed at the end. Nothing is redundant or padded.

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 simple four-parameter, all-required tool with full schema coverage and no output schema, the essentials are present. But a mutation tool with zero annotations should at least state scope of application (all pages?) and output behavior, which are missing.

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%, so every parameter is already documented in the schema, and the description adds no further meaning such as accepted position values beyond 'top'/'bottom' or formatting syntax for text. Baseline 3 applies when the schema does the heavy lifting.

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 specific verb and resource ("Adds a header or footer to a PDF"), which is unambiguous and distinguishable from the conversion/extraction siblings. It does not explicitly contrast with any alternative, but the operation itself is narrow enough that no confusion arises.

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 guidance on when to use this versus other PDF-mutation tools (e.g. pdf_annotate, which could also stamp text onto pages), and no prerequisites or exclusions. The agent must infer usage entirely from the name and one-line purpose.

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