Skip to main content
Glama

pdf-suite

pdf_split

Split a PDF by page range or page chunk size into an extracted PDF slice plus per-range metadata.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pdf_split"
  }
}

Input Schema

NameRequiredDescriptionDefault
pagesNo1-based page range, e.g. "1-2".1
inputPathNo
base64DataNo
outputPathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 output shape ('an extracted PDF slice plus per-range metadata'), which is valuable since there is no output schema. It says nothing about whether the source document is modified or preserved, or what happens when the outputPath is omitted.

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, and the two modes are stated up front. Its compactness works against it only because one of the promised modes has no schema support.

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?

A four-parameter mutating-style file tool with no annotations, no output schema, and 25% schema coverage needs far more: input source precedence, default behavior for pages='1', and where the slice is written. The unresolved chunk-size claim leaves the definition incomplete and partly inaccurate.

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 coverage is only 25%, with just 'pages' documented, so the description must compensate for the three undocumented parameters and does not. Worse, it advertises a 'page chunk size' mode that has no corresponding parameter in the schema, actively misleading the agent about available inputs.

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 uses a specific verb and resource ('Split a PDF') and names two operating modes, page range and chunk size. It does not, however, distinguish itself from the sibling pdf_extract_pages, which an agent could easily confuse with this tool.

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 guidance on when to use this tool rather than pdf_extract_pages, pdf_remove_pages, or the other slice-related siblings, and no exclusions. It also never says when to supply inputPath versus base64Data, which is the first decision an agent must make.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources