Skip to main content
Glama
keenanlk

stayput-mcp

by keenanlk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Rotate PDF pages

rotate_pdf

Rotate all or selected PDF pages clockwise by 90, 180, or 270 degrees and save the result as a new PDF without altering the original.

Instructions

Rotate all pages, or only the listed ones, clockwise by 90, 180 or 270 degrees, and save the rotation permanently in a new PDF. The input is not modified and an existing file is never overwritten; returns the new path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYesPath to the PDF.
pagesNoPages to rotate, for example "1, 3-4". Default: every page.
outputNoWhere to write the result. Defaults to a new file beside the input. Existing files are never overwritten; a free name like file-1.pdf is used instead.
degreesYesClockwise rotation to add.
passwordNoPassword for a PDF that asks for one when opened. Used only on this machine.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Adds valuable context beyond annotations: states input is not modified, existing files are never overwritten, and returns a new path. Annotations declare non-destructive and non-readOnly, but the description clarifies safety and output behavior.

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?

Single sentence, front-loaded with core action and constraints, no wasted words. Efficiently communicates scope, limits, and output behavior.

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?

Covers key behavioral aspects like input preservation and output path creation. Lacks details on error handling or password usage, but with no output schema and full schema coverage, it is nearly complete for an agent's needs.

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 coverage is 100%, so parameters are fully documented in schema. Description adds no new parameter details beyond what schema provides, such as defaults or format examples. Baseline 3 is appropriate.

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) plus resource (PDF pages) with details on scope (all pages or listed ones), rotation values, and permanent save. Clear enough to distinguish from siblings like split_pdf or merge_pdfs.

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?

Implies use for permanent page rotation, but doesn't explicitly name alternatives or when not to use it. Sibling tools handle different operations, so context is clear, but no exclusions are provided.

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