Skip to main content
Glama

pdf-suite

pdf_extract_pages

Extract and reorder specific 1-based pages from a PDF into a new PDF file.

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

Input Schema

NameRequiredDescriptionDefault
pagesNoPages/order to extract e.g. "1,3-4".1
inputPathNo
base64DataNo
outputPathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose one useful trait — the operation produces a new PDF rather than mutating the source — but says nothing about permissions, error handling for out-of-range page numbers, ordering conflicts, or what happens if 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 no redundancy. It is efficient, though efficiency tips into under-specification given the four parameters and zero annotations.

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?

For a four-parameter file-transformation tool with no annotations and no output schema, this description is too thin. It never explains the inputPath vs base64Data choice, the required outputPath, or the default of pages="1", all of which an agent needs before calling it correctly.

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%; only the pages parameter has a schema description. The description usefully adds the 1-based indexing and reordering semantics for pages, but inputPath, base64Data, and outputPath are undocumented in both schema and description, leaving the two alternate input sources and the output destination entirely unexplained.

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 concrete verb pair ("Extract and reorder") plus the resource ("specific 1-based pages from a PDF") and the result ("into a new PDF file"). An agent can distinguish this from pdf_remove_pages by the word "extract," but the description never names that inverse sibling, so the differentiation is implicit rather than stated.

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 when-to-use guidance, no prerequisite information, and no mention of alternatives such as pdf_remove_pages or pdf_split. The only hint is "1-based pages," which implies the tool selects rather than removes pages, but the agent must infer that.

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