Skip to main content
Glama

pdf_bates

Add Bates numbering to a PDF with configurable prefix, padding, start number, and placement to label legal or archival documents consistently.

Instructions

Adds Bates numbering 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>",
      "start_number": "<start_number>",
      "prefix": "<prefix>",
      "padding": "<padding>"
    },
    "name": "pdf_bates"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesThe input PDF file path.
outputYesThe output PDF file path.
prefixYesPrefix.
paddingYesPadding length.
positionNoPosition (bottom-right, bottom-left, bottom-center, top-right, top-left, top-center). Default: bottom-right.
start_numberYesStart number.

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 supplied, so the description carries the full behavioral burden, yet it only states input and output file types. It does not say whether numbering applies to all pages, whether the input file is left untouched, whether the output path is overwritten, or whether fonts/placement are configurable beyond the schema fields.

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 short sentences with the action front-loaded and the I/O contract appended. The bracketed format line is somewhat boilerplate but does convey that the tool is PDF-in/PDF-out, which is useful at a glance.

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 six-parameter mutation tool with no annotations and no output schema, the description is thin: it never covers side effects, page scope, or failure modes. The complete schema descriptions compensate for parameter coverage, keeping this at minimum viable rather than inadequate.

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 including the optional position field is documented in the schema. The description adds no meaning beyond that — for example, no guidance on padding length conventions or prefix formatting — so the baseline of 3 applies.

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 names a specific verb and resource ('Adds Bates numbering to a PDF'), which is unambiguous and clearly distinct from sibling operations like pdf_annotate or pdf_compress. It does not explicitly contrast with siblings, but the operation itself is narrow enough that an agent can select it without opening the schema.

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 or exclusions. The agent must infer from the name alone that this is for legal/document-control numbering rather than general page labeling.

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