Skip to main content
Glama

pdf_nup

Impose multiple PDF pages onto one sheet using 2-, 4-, 9-, or 16-up grid layouts and output a new PDF.

Instructions

N-Up Page Imposition: Combine multiple pages per sheet in a 2, 4, 9, or 16-up grid layout. [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_nup"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
outputYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses the input/output formats (.pdf to .pdf) and the resulting grid sizes, but says nothing about how the 2/4/9/16-up choice is actually made — the schema exposes no such parameter — nor whether the output overwrites an existing file, whether the source is preserved, or how page margins/scaling are handled.

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 clauses: the operation and its grid options are front-loaded, followed by an economical input/output format tag. Nothing is wasted, though the bracketed format notation is somewhat mechanical and the layout list creates an unanswered question rather than resolving one.

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?

There is no output schema and no annotations, so the description must stand alone, and for a simple two-path transform it covers the essentials: what it produces and the file types involved. It is incomplete on the point an agent most needs — how to select the 2/4/9/16-up layout — and on write/overwrite behavior.

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 both required parameters, so the description must compensate. The bracketed '[Input: .pdf | Output: .pdf]' does at least constrain both parameters to PDF paths, but neither is described in terms of what value to supply (file path, page range, etc.). Worse, the description advertises layout options that map to no parameter at all, leaving the agent unsure how to request one.

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 operation (N-Up page imposition / combining multiple pages per sheet) with concrete layout options, which is clearly distinguishable from conversion siblings like img_to_pdf or text-extraction siblings. It stops short of contrasting with the nearest relative (pdf_booklet), so it is clear but not fully sibling-differentiated.

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

Usage Guidelines3/5

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

Usage is only implied by the operation itself — an agent can infer 'use this to impose pages onto fewer sheets', but there is no explicit when-to-use, no when-not-to-use, and no pointer to alternatives such as pdf_booklet for booklet-style imposition. No prerequisites or constraints on the input PDF are stated.

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