Skip to main content
Glama

pdf_posterize

Tiles oversized PDF pages across a grid of standard printable sheets with overlap margins and cut guides, so large posters can be printed on a regular home or office printer.

Instructions

Multi-Sheet Poster Tile Slicer: Tile oversized PDF pages across a grid of standard printable sheets with overlap margins and cut guides [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_posterize"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
scaleNo
outputYes
grid_colsNo
grid_rowsNo
overlap_ptNo
target_sheetNo
include_guidesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full disclosure burden. It does convey real behavior — tiling across a grid, overlap margins for gluing, and cut guides — which is meaningful beyond a restatement of the name. It omits whether output is a new file or overwrites input, whether grid dimensions auto-compute from scale, and how scale interacts with the grid.

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 front-loaded sentence with the core operation first and the format tag last; no filler. The colon-prefixed 'Multi-Sheet Poster Tile Slicer' label is slightly redundant with the tool name but serves as a quick gloss.

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 an 8-parameter transformation tool with no annotations and no output schema, the definition covers the conceptual operation well but leaves key call-time decisions (scale meaning, grid vs scale precedence, sheet-size defaults) undocumented. An agent could pick the right tool but would likely have to guess at parameter values.

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 0% across 8 parameters, so the description must compensate and only partly does. It gives semantic grounding for grid_cols/grid_rows ('grid'), overlap_pt ('overlap margins'), include_guides ('cut guides'), and target_sheet ('standard printable sheets'), plus input/output formats, but leaves 'scale' entirely unexplained and gives no units, ranges, or defaults for the numeric fields.

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: 'Tile oversized PDF pages across a grid of standard printable sheets.' That clearly separates it from neighbors like pdf_crop (trim a page) and pdf_booklet (imposition), even though no sibling is named explicitly. The Input/Output format tag reinforces that it produces a PDF.

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?

The use case is implied — an oversized page that must be printed across multiple sheets — but there is no explicit when-to-use statement, no mention of when to prefer pdf_crop or pdf_booklet instead, and no note about what happens to pages that already fit a standard sheet.

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