Skip to main content
Glama

pdf_split

Split a PDF into multiple single-page PDF files by specifying the input document and an output directory for the separated pages.

Instructions

Splits a PDF into multiple single-page PDFs. [Input: PDF (.pdf) | Output: Multiple .PDFs]

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_dir": "<output_dir>"
    },
    "name": "pdf_split"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesThe input PDF file path.
output_dirYesThe directory where split pages will be saved.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 behavioral burden and does not discharge it. It never states how output files are named, whether existing files in output_dir are overwritten, what happens with encrypted or malformed PDFs, or whether the directory must already exist. Only the broad output shape ('Multiple .PDFs') is disclosed.

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, front-loaded with the core action and followed by a compact input/output tag. No filler. The bracketed format line slightly duplicates information the schema and purpose sentence already convey, which keeps it from a 5.

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 tool with a fully documented schema and no output schema, this is minimally adequate: the agent knows what it does and what to pass. The missing piece is any statement about how the resulting page files are named or where exactly they land within output_dir, which matters for chaining into a follow-up tool.

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 100%, so both parameters (input, output_dir) are already documented in the schema and the baseline is 3. The description adds no naming convention, path format, or constraint detail beyond what the schema says, so it neither compensates nor detracts.

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 resource: 'Splits a PDF into multiple single-page PDFs' plus an input/output format tag. That is unambiguous about what the tool does. It stops short of distinguishing itself from close siblings such as pdf_burst, pdf_extract_pages, pdf_chunk, pdf_split_by_outline and pdf_split_scanned_book, so an agent cannot tell which splitter to pick from this text alone.

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, and no mention of the sibling splitters that would be the obvious alternatives. Nothing indicates when a plain single-page split beats an outline-based, extract-pages or chunk-based approach, so the agent must infer selection from the tool name.

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