Skip to main content
Glama

pdf_split_by_outline

Split multi-chapter PDFs by bookmark outline into separate files and package the output as a ZIP.

Instructions

Split PDF by Outline: Split multi-chapter PDF documents based on their /Outlines bookmark hierarchy [Input: .pdf | Output: .zip]

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_by_outline"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
outputYes

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?

With no annotations, the description carries the full burden, and it does disclose the mechanism and both file formats (PDF in, ZIP out), which tells the agent this is a non-destructive read-then-archive operation producing multiple files. It says nothing about what happens when a PDF has no /Outlines, which bookmark level triggers a split, or how output files are named, which are the main behavioral risks here.

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: name, mechanism, then I/O formats in brackets. Nothing is redundant, though the colon-restatement of the tool name adds little beyond the mechanism clause that follows it.

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 two-parameter tool with no output schema and no annotations, the description covers purpose, mechanism, and formats, which is close to sufficient. It is missing the edge-case behavior (no bookmarks present) and output layout, both of which an agent would need to set expectations correctly.

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 coverage is 0% for two required parameters, so the description must compensate; the bracketed "[Input: .pdf | Output: .zip]" does establish that both parameters are file paths and constrains their formats. That is useful but minimal — no indication of whether paths are local, whether the output may be a directory, or what happens on overwrite.

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 (split a PDF) plus the exact mechanism (/Outlines bookmark hierarchy), which distinguishes it from the generic pdf_split and from pdf_split_scanned_book by content type. It stops short of naming those siblings, but the mechanism alone is enough for an agent to tell them apart.

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?

"Split multi-chapter PDF documents based on their /Outlines bookmark hierarchy" implies the precondition (the file must carry bookmarks) and thus when to pick this over a page-range split. However, there is no explicit exclusion for PDFs without outlines and no named alternative for that case, so the guidance is implied rather than stated.

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