Paperboy

Official

Overview Schema Source Related Servers Discussions Admin

rotate_pages

DestructiveIdempotent

Rotate PDF pages clockwise by 90, 180, or 270 degrees; omit page selection to rotate all pages, with password support for protected files.

Instructions

Rotate pages clockwise by 90/180/270 degrees (all pages if pages omitted). Needs the owner password if the PDF forbids document assembly. Signed PDFs are refused.

Any password argument can be "ask": the user then types it on a local page, so it never passes through the chat.

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_path": "<input_path>",
      "degrees": "<degrees>"
    },
    "name": "rotate_pages"
  }
}

Input Schema

Name	Required	Description	Default
`pages`	No
`degrees`	Yes
`password`	No
`overwrite`	No
`input_path`	Yes
`output_path`	No

Output Schema

Name	Required	Description	Default
`output`	Yes
`rotated_pages`	Yes
`password_protected`	Yes
`user_password_changed`	Yes
`permissions_restricted`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.1Nov 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "output": {
+      "title": "Output",
+      "type": "string"
+    },
+    "password_protected": {
+      "title": "Password Protected",
+      "type": "boolean"
+    },
+    "permissions_restricted": {
+      "title": "Permissions Restricted",
+      "type": "boolean"
+    },
+    "rotated_pages": {
+      "items": {
+        "type": "integer"
+      },
+      "title": "Rotated Pages",
+      "type": "array"
+    },
+    "user_password_changed": {
+      "title": "User Password Changed",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "password_protected",
+    "permissions_restricted",
+    "user_password_changed",
+    "output",
+    "rotated_pages"
+  ],
+  "title": "RotateResult",
+  "type": "object"
+}

First observedv0.1.0Oct 21, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true; the description adds real context beyond that: the owner-password requirement, refusal of signed PDFs, and the "ask" password flow that keeps secrets out of chat. It does not explain the destructive/overwrite implications (i.e., whether the original file is modified), which is the main remaining gap.

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?

Four short, front-loaded sentences with no filler; the core operation leads and constraints follow. The password "ask" note applies broadly across tools, but it is still useful safety context here.

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?

An output schema exists, so return values need not be described, and the safety profile is partly covered by annotations. However, with a destructive write tool and 0% schema coverage, the missing description of output_path and overwrite semantics leaves an agent unable to predict whether the source PDF is modified.

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 0% across 6 parameters, so the description must carry the load. It meaningfully documents pages, degrees, and password (including the "ask" sentinel), but says nothing about input_path, output_path, or overwrite, leaving half the parameters unclarified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (rotate), the resource (pages), the allowed values (90/180/270 clockwise), and the default scope (all pages if pages omitted). This is clearly distinct from siblings like rearrange_pages or resize_pages.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear default behavior when pages is omitted and states preconditions (owner password needed if document assembly is forbidden, signed PDFs refused). It does not explicitly compare against alternatives, but rotation has no true sibling substitute in the catalog.

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