FreeDailyPro PDF Tools

pdf_split

Read-onlyIdempotent

Split a PDF into multiple files by page range, or combine specific ranges into one reordered file

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": {
      "fileBase64": "<fileBase64>",
      "ranges": "<ranges>"
    },
    "name": "pdf_split"
  }
}

Input Schema

Name	Required	Description
`ranges`	Yes	Semicolon-separated groups, each a comma-separated list of pages/ranges, e.g. '1-3,5;7-9' for two output files
`fileBase64`	Yes	The input file as a base64 string, without a data: prefix.
`combineIntoOne`	No	If true, combines all specified ranges into a single reordered PDF instead of one file per group

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 13, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / fileBase64 / description
```
Added value: +"The input file as a base64 string, without a data: prefix."
```
First observedOct 24, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so safety and idempotency are covered. The description adds nothing about where output files go, how they are named, how the source file is treated, or what happens with invalid/out-of-range page numbers — useful context that is simply absent with no output schema to fall back on.

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 covering both modes with no filler or repetition. It is efficient, though it stops short of the compactness-plus-guidance that would make it a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-parameter, no-output-schema tool with full annotation coverage, the description tells the agent the two modes of operation and that ranges drive splitting. Some gaps remain around output artifact naming and validation behavior, but nothing prevents a correct invocation.

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 all three parameters (ranges, fileBase64, combineIntoOne) are already documented with syntax and examples. The description only restates 'page range' and 'combine ranges into one reordered file', adding no syntax, constraints, or format detail beyond the schema — baseline 3 applies.

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?

Uses a specific verb and resource ('Split a PDF into multiple files') and names the two operating modes: per-range splitting and combining ranges into one reordered file. It is clearly distinguishable from pdf_merge and pdf_extract_pages in intent, though it never names those siblings to route the agent.

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?

The description implies when each mode applies ('by page range' vs 'combine specific ranges into one reordered file'), but gives no explicit when-to-use/when-not-to-use guidance and no alternatives such as pdf_extract_pages for pulling out a single range or pdf_merge for joining separate documents.

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

All FreeDailyPro PDF Tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?