Skip to main content
Glama

pdf_burst

Split a PDF into individual files and return the path of each, saving all outputs to a specified directory for offline document workflows.

Instructions

Bursts a PDF into individual files, returning the path of each.

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

Input Schema

NameRequiredDescriptionDefault
inputYesThe input PDF file path.
output_dirYesThe directory where individual files will be saved.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/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. It does disclose one useful behavioral fact beyond the schema: the tool returns the path of each produced file. It says nothing about naming of output files, whether output_dir must pre-exist, overwrite behavior, or handling of non-page content, which matters for a filesystem-writing tool.

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 with no filler; the return-value clause is appended efficiently. It is arguably too terse rather than too verbose, but nothing is wasted.

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 described schema and no annotations the description covers the core action and return shape. Without an output schema it still omits details an agent would want, such as output file naming and side effects on an existing directory, so it is adequate but incomplete.

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 are already documented in the input schema and the description adds no additional meaning (no path format, no relative-vs-absolute, no directory creation semantics). Baseline 3 applies when the schema does the heavy lifting.

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 gives a specific verb ('bursts') plus the resource ('a PDF') and the output ('individual files ... path of each'), which is enough to distinguish it from converters like html_to_pdf or transforms like pdf_compress. It stops short of differentiating it from adjacent page-level tools such as pdf_extract_pages or pdf_chunk, which an agent reading only this text could confuse it with.

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 explicit when-to-use or when-not-to-use guidance and no named alternative. The use case is only implied by the verb 'bursts', leaving the agent to infer whether this is for per-page splitting versus range extraction or chunking.

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