Skip to main content
Glama
PurpleDirective

quillpdf-mcp

by PurpleDirective
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Bates-number a PDF

pdf_bates

Stamps sequential Bates numbers with a custom prefix and zero-padding on every PDF page, writing the numbered file locally without sending it over the network.

Instructions

Stamp sequential Bates numbers ({prefix}{zero-padded n}) on every page. Runs entirely on this machine — the file is read and written locally and never sent anywhere.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
colorNoColor as #RRGGBB (default #000000)
forceNoReplace the output file if it already exists (default: refuse, so existing files are never silently clobbered)
inputYesPath to the input PDF
outputYesPath to write the numbered PDF
prefixNoText before the number (default none)
fontSizeNoFont size in points (default 10)
padWidthNoZero-pad width (default 6)
positionNoCorner (default bottom-right)
startNumberNoFirst number (default 1)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • addedInput schema / properties / force
      Added value: +{
+  "description": "Replace the output file if it already exists (default: refuse, so existing files are never silently clobbered)",
+  "type": "boolean"
+}
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare the write/idempotency/destructive profile (readOnly=false, idempotent=false, destructive=false). The description adds genuinely new context: the operation runs entirely on this machine and the file is read and written locally and never transmitted, which is real behavioral information not derivable from annotations or schema.

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 sentences, zero filler, with the core action front-loaded and the privacy guarantee as a supporting clause. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 100% schema coverage and no output schema, the description needn't restate parameters or return values. It covers purpose and the local-processing guarantee well; the only real gap is sibling disambiguation against pdf_page_numbers.

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?

Schema coverage is 100%, so the baseline is 3. The description earns a bump by explaining the composed format "{prefix}{zero-padded n}", which conveys how the prefix and padWidth parameters interact in the stamped output — a relationship the schema states only in isolation.

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 gives a specific verb and resource ("Stamp sequential Bates numbers") and scope ("on every page"). It's clear what the tool does, but it never distinguishes itself from the close sibling pdf_page_numbers, so an agent gets no help telling the two apart.

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 guidance, no prerequisites, and no mention of alternatives like pdf_page_numbers or pdf_watermark. The agent is left to infer that this is the legal-numbering variant purely from the name.

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

Deploy Server

Other Tools