Skip to main content
Glama

pdf_booklet

Reorder and impose PDF pages for 2-sided folding booklet printing, turning a standard PDF into a print-ready booklet PDF.

Instructions

Booklet Imposition: Reorder and impose pages for 2-sided folding booklet printing. [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_booklet"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
outputYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description must carry the full behavioral burden. It states the transformation and file types, but does not disclose overwrite behavior, page-count requirements, blank-page insertion, permissions, or error handling for a file-producing operation.

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 short clauses and a compact I/O tag; the purpose is front-loaded and every element contributes without repetition.

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 simple two-parameter PDF transform, the description covers the core operation and file types. However, with no annotations or output schema, it omits imposition-specific constraints and output handling details that would make invocation fully unambiguous.

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?

The schema contains only two bare string parameters with 0% description coverage. The description adds that both are .pdf files, compensating for type ambiguity, but it does not clarify path semantics, overwrite/creation behavior, or other input/output constraints.

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 ('Booklet Imposition: Reorder and impose pages') and its intended result ('2-sided folding booklet printing'), plus input/output file types. This clearly distinguishes it from conversion, extraction, or security siblings, though it does not explicitly name an alternative tool.

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?

It gives the intended use case—booklet printing from a PDF—but does not specify when to choose it over other PDF tools, prerequisites, or when not to use it. Usage is implied rather than explicitly routed.

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