PDFops

Rotate PDF pages

pdf_rotate

Idempotent

Rotate pages of a PDF clockwise by 90, 180 or 270 degrees (or -90). Rotation adds to each page's existing rotation. Omit pages to rotate every page. Use this to fix sideways scans. Returns the result inline as an application/pdf resource; the source is never modified.

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": {
      "pdf_path": "<pdf_path>",
      "degrees": "<degrees>"
    },
    "name": "pdf_rotate"
  }
}

Input Schema

Name	Required	Description
`pages`	No	1-based page spec such as "1-3,5"; default all pages
`degrees`	Yes	Clockwise rotation to add
`password`	No	Password to open the input, only needed for a user-password PDF (owner-locked files with an empty user password open without it).
`pdf_path`	Yes	PDF source: an https:// URL or a data:application/pdf;base64,… URI (this hosted server cannot read local file paths).

Output Schema

Name	Required	Description	Default
`bytes`	Yes	Size of the produced PDF in bytes
`resource_uri`	No	pdfops:// uri of the inline application/pdf resource

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Goes beyond annotations by disclosing that rotation is additive to each page's existing rotation, that the result comes back inline as an application/pdf resource, and that the source is never modified. That last point squares with openWorldHint and non-destructive hints rather than contradicting them; only pagination/size limits of the returned resource are unaddressed.

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?

Four tight sentences, front-loaded with the operation and angle options, followed by defaults, use case, and return behavior. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a full output schema and annotations already covering the safety profile, the description supplies the remaining pieces an agent needs: additive semantics, page-default behavior, and output delivery format. Nothing essential to correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning beyond the schema: the additive rotation semantics and the -90 equivalency for the degrees enum. It also restates the pages default, which is already in the schema, hence not a 5.

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 of a PDF') plus the accepted angle set, and is clearly distinct from siblings like pdf_merge or pdf_extract_pages. An agent knows exactly what the tool does without opening the schema.

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 clear usage context ('Use this to fix sideways scans') and a default-behavior rule ('Omit pages to rotate every page'). It does not name a sibling alternative or state when not to use it, but the operation is unambiguous enough that little routing ambiguity remains.

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

All PDFops tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?