Skip to main content
Glama

pdf_reorder_pages

Rearrange PDF pages into a new order by specifying a 1-based sequence, then save the result to a separate file.

Instructions

Reorders pages. [Input: PDF (.pdf) | Output: PDF (.pdf)]

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>",
      "order": "<order>",
      "output": "<output>"
    },
    "name": "pdf_reorder_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesThe input PDF file path.
orderYesThe new 1-based page order, e.g., '3,2,1'.
outputYesFile path for the reordered output.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure but only states input and output formats. It does not mention whether the output overwrites an existing file, whether order length must match page count, how invalid page numbers are handled, or any permission/encryption requirements.

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?

The description is front-loaded and waste-free, with the bracketed format note adding quick context. It is terse rather than verbose, though the extreme brevity leaves informational gaps.

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 PDF transformation with complete schema descriptions, the definition is minimally adequate. However, without annotations or an output schema, it should say more about output behavior and validation constraints to be fully complete.

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 are documented in the schema, including the 1-based order example. The description adds no parameter meaning beyond that baseline.

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 states a specific verb and resource ('Reorders pages') and the input/output format (PDF to PDF). It is clear enough to distinguish from siblings like pdf_delete_pages or pdf_extract_pages, though it does not explicitly call out alternatives.

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 versus alternatives, no prerequisites, and no exclusions. The only context is the input/output file type, which is already implied by the tool name and schema.

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