Skip to main content
Glama

pdf-suite

pdf_rotate

Permanently rotate all or selected pages of a PDF by 90, 180, or 270 degrees clockwise.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pdf_rotate"
  }
}

Input Schema

NameRequiredDescriptionDefault
angleNo
pagesNoOptional 1-based page filter (defaults to all pages).
inputPathNo
base64DataNo
outputPathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the key behavioral trait that rotation is permanent and clockwise, which is genuinely useful. However, it says nothing about whether the file is modified in place or written to outputPath, how inputPath and base64Data interact, or what happens on invalid page numbers.

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?

A single well-formed sentence with the operation, scope, and value constraints front-loaded. No filler or redundant restatement of the name.

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

Completeness2/5

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

With no annotations, no output schema, and five parameters at 20% coverage, the description should clarify the input-source choice and output destination. Those gaps are material for a mutation tool that permanently alters a file, so the definition is not complete enough to invoke confidently.

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

Parameters2/5

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

Schema coverage is only 20%: only 'pages' is documented in the schema, and the description merely restates its all-vs-selected semantics. The three most consequential parameters (inputPath, base64Data, outputPath) are undocumented in both schema and description, leaving the agent to guess which input source is required and where the result lands.

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), resource (PDF pages), scope (all or selected pages), and the exact permitted values (90/180/270 clockwise). It is unmistakable against siblings like pdf_crop_margins or pdf_extract_pages, which do different transformations.

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?

The phrase 'all or selected pages' implies the scope decision an agent faces, but there is no explicit when-to-use guidance, no exclusions, and no naming of alternatives. Usage is inferable from the operation rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources