Skip to main content
Glama

pdf_stitch_canvas

Combine multiple PDF pages vertically or horizontally into one continuous single-page canvas, with optional margins and spacing, and save the result as a new PDF.

Instructions

Stitch Continuous Canvas: Combine multiple pages vertically or horizontally into a continuous single-page canvas. [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_stitch_canvas"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
outputYes
directionNovertical
margin_ptNo
spacing_ptNo

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 only says the result is a single-page canvas. It does not state whether page order is preserved, how differing page sizes are reconciled, whether the operation is lossless, or what the response looks like. The input/output format tags are useful but minimal.

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 core operation front-loaded and the format tags trailing. The leading 'Stitch Continuous Canvas' label largely restates the tool name, a minor redundancy, but nothing else is wasted.

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?

For a five-parameter, unannotated, no-output-schema tool, the description is thin. It leaves the two layout parameters (margin_pt, spacing_pt) and their defaults unexplained and gives no behavioral or return-value context to compensate for the missing annotations.

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. The description covers only the direction concept (vertical vs horizontal), which the enum already conveys, and says nothing about margin_pt, spacing_pt, or that input/output are file paths. Two parameters are entirely undocumented anywhere.

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 states a specific verb and outcome: combine multiple pages vertically or horizontally into a continuous single-page canvas. That is clearly distinguishable from siblings like pdf_booklet or pdf_compare, though it does not explicitly name an alternative to disambiguate.

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 or when-not-to-use guidance. With siblings such as pdf_booklet, pdf_crop, and pdf_extract_pages nearby, an agent gets no help deciding when stitching is the right operation versus another page-composition tool.

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