Skip to main content
Glama

pdf_rotate

Rotate all or selected pages in a PDF by 90, 180, or 270 degrees, then save the adjusted document to a new PDF file.

Instructions

Rotates pages in a PDF. [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>",
      "pages": "<pages>",
      "angle": "<angle>",
      "output": "<output>"
    },
    "name": "pdf_rotate"
  }
}

Input Schema

NameRequiredDescriptionDefault
angleYesThe angle to rotate by, typically 90, 180, or 270.
inputYesThe input PDF file path.
pagesYesThe pages to rotate, either 'all' or specific pages like '1,3'.
outputYesFile path for the rotated output.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose the transformation contract ([Input: PDF | Output: PDF]) and the required output path is in the schema, but it never says whether the rotation is absolute or cumulative, whether the source file is left untouched, or what happens on an invalid angle.

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?

Two compact clauses: the action first, then the bracketed I/O contract. Zero filler and the essential information is front-loaded.

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?

For a simple four-parameter, fully-documented, non-destructive-looking transform with no output schema, the definition covers the action, the parameter meanings (via schema), and the return artifact type. The remaining gap is behavioral detail and sibling routing rather than anything blocking correct invocation.

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 four parameters (angle, input, pages, output) are already documented with examples such as '90, 180, 270' and '1,3'. The description adds nothing 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 gives a specific verb and resource ("Rotates pages in a PDF") plus the input/output file types, so the agent knows exactly what operation is performed. It stops short of differentiating from the sibling pdf_auto_rotate, leaving the agent to guess which rotation tool to pick.

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, when-not-to-use, or prerequisite guidance at all. The obvious ambiguity with the sibling pdf_auto_rotate (manual angle vs. automatic detection) is never addressed.

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