Skip to main content
Glama

pdf_split_scanned_book

Split two-up scanned book pages into single pages by detecting the center binding gutter. Convert a PDF of scanned spreads into individual page PDFs.

Instructions

Split Scanned Book Spine: Detect center binding gutter spine and split two-up page scans into single pages. [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_split_scanned_book"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
outputYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the core behavior (gutter detection before splitting) plus input/output formats. It omits important behaviors for a file-writing operation: what happens when no gutter is detected, whether the output overwrites, and whether page order/orientation is preserved.

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 sentences plus a format tag, with the specific capability front-loaded. The bracketed shorthand is a bit brittle but wastes no words.

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 mutation tool with no annotations, no output schema, and completely undocumented parameters, the definition is too thin. An agent still cannot tell what the output artifact looks like (one file vs. many), how failures are signaled, or what constraints the input must satisfy.

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 two required string parameters, so the description must compensate and it largely doesn't. The '[Input: .pdf | Output: .pdf]' note confirms file types but says nothing about path semantics, output naming, or whether 'output' is a directory or a single merged file.

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 verb and resource ('split two-up page scans into single pages') and a concrete mechanism ('detect center binding gutter spine'), which is far more specific than the sibling pdf_split. It doesn't explicitly say how it differs from pdf_split, but the scanned-book/gutter framing makes the intended use case unambiguous.

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 implied by the description: it applies to two-up scans of bound books where the gutter must be detected. There is no explicit guidance about when to prefer it over pdf_split or pdf_burst, nor any statement of prerequisites such as scan quality or spread orientation.

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