Skip to main content
Glama

pdf-suite

pdf_add_page_numbers

Stamp vector pagination or Bates numbers (e.g. "Page X of Y") onto every PDF page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pdf_add_page_numbers"
  }
}

Input Schema

NameRequiredDescriptionDefault
prefixNoPage
inputPathNo
base64DataNo
outputPathNo
startNumberNo

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 burden, yet it does not say whether the source file is modified in place or written to outputPath, what happens if both inputPath and base64Data are given, or whether Y in 'Page X of Y' is auto-computed. Only the 'vector' and 'every page' traits are disclosed.

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?

A single well-formed sentence with the core action front-loaded and no filler. It is efficient but leaves obvious gaps that a second sentence could have closed.

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?

With five undocumented parameters, no annotations, and no output schema, the definition leaves the agent unable to determine input sourcing or output behavior for a mutation operation. The core concept is conveyed but the invocation details are not.

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% across five parameters, and the description compensates only weakly: the example 'Page X of Y' hints at the prefix default and an auto-computed total. Nothing explains startNumber, inputPath, base64Data, or outputPath, which are the parameters an agent most needs to get right.

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 (stamp) and a specific resource (vector pagination or Bates numbers) and the scope (every PDF page), with a concrete example format. It does not explicitly distinguish itself from the sibling pdf_add_watermark, which is the nearest overlapping tool.

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 choose this over pdf_add_watermark, no prerequisites, and no mention of how the two input modes (inputPath vs base64Data) should be selected. The reader must infer all selection logic from the name.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources