Skip to main content
Glama

Разделить PDF

split_pdf

Разделяет PDF на части. Результат — ZIP-архив с PDF-файлами. file_url: публичный URL PDF-файла. mode: every-page (по умолчанию) | half | ranges. ranges: диапазоны при mode=ranges, например "1-3,5-7,10".

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": {
      "file_url": "<file_url>"
    },
    "name": "split_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoevery-page
rangesNo
file_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so safety framing is covered; the description adds that the output is a ZIP of PDFs and that the input must be a publicly reachable URL. It says nothing about file-size limits, URL fetch failures, or how ranges are handled when mode is not 'ranges'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short lines, front-loaded with the action and the output form, then one line per parameter. No filler or redundancy.

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?

The tool is simple, an output schema exists, and the description still explains the return container. The remaining shortfall is sibling routing in a suite of ~48 PDF tools, where splitting vs page extraction is a real choice the description leaves undecided.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and does so: file_url is a public PDF URL, mode has three named values with every-page as default, and ranges is documented with a concrete syntax example ("1-3,5-7,10"). The only gap is not stating that ranges is ignored unless mode=ranges.

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 ("Разделяет PDF на части") and adds the concrete result form (ZIP archive of PDFs), so the action is unambiguous. It does not distinguish itself from the closest sibling, extract_pages, which also takes a page selection but returns a single PDF rather than a ZIP of parts.

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?

Usage is only implied through the mode enumeration (every-page / half / ranges); the description never says when to pick this over extract_pages or merge_pdfs. There are no stated prerequisites beyond the URL being public.

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.