Skip to main content
Glama
PurpleDirective

quillpdf-mcp

by PurpleDirective
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Rotate PDF pages

pdf_rotate

Rotate selected or all PDF pages by a 90-degree multiple. Runs locally; files stay on your machine.

Instructions

Rotate pages by a multiple of 90 degrees. Omit pages to rotate every page. Runs entirely on this machine — the file is read and written locally and never sent anywhere.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
angleYesRotation in degrees; must be a multiple of 90 (e.g. 90, 180, -90)
forceNoReplace the output file if it already exists (default: refuse, so existing files are never silently clobbered)
inputYesPath to the input PDF
pagesNo1-based pages to rotate (default: all)
outputYesPath to write the rotated PDF

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • addedInput schema / properties / force
      Added value: +{
+  "description": "Replace the output file if it already exists (default: refuse, so existing files are never silently clobbered)",
+  "type": "boolean"
+}
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations declare the safety profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false), and the description adds genuinely new context: processing is entirely local with no remote transmission. It does not detail return behavior or the clobber/force semantics, but it goes beyond the annotations where it matters most for trust.

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?

Three short sentences, each earning its place: the operation and its constraint are front-loaded, followed by the default-page rule and the local-processing guarantee. No filler.

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?

No output schema exists, so the description could say more about what is returned after the write, but for a straightforward local file transform the essentials (constraint, default scope, privacy) are covered and the annotations carry the safety profile.

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 every parameter (angle, force, input, output, pages) is already documented in the schema. The description only restates the pages default and the 90-degree constraint, adding no syntax or format detail beyond the schema.

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 and resource ("Rotate pages") plus the operative constraint ("by a multiple of 90 degrees"). Rotation is unique among the sibling set, so no sibling can be confused with it, and an agent knows exactly what the tool produces.

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?

"Omit `pages` to rotate every page" gives a usage rule for one parameter, but there is no when-to-use/when-not framing and no mention of alternatives (e.g. pdf_organize) for reordering vs. rotating. Usage is implied rather than guided.

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

Deploy Server

Other Tools