Skip to main content
Glama

pdf_auto_rotate

Detect text baseline and rotation angle in a PDF to correct page orientation and output an upright PDF.

Instructions

Auto Upright Orientation: Heuristically detect text baseline and rotation angle to automatically upright pages. [Input: .pdf | Output: .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>",
      "output": "<output>"
    },
    "name": "pdf_auto_rotate"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
outputYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden itself. It discloses that detection is heuristic and that input/output are both .pdf, but says nothing about accuracy limits, what happens to already-upright pages, whether output may overwrite input, or failure behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences with the mechanism front-loaded and the I/O contract clearly bracketed at the end. Minor redundancy between 'Auto Upright Orientation' and 'automatically upright pages' is the only waste.

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

Completeness3/5

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

Given no annotations, no output schema, and two fully undocumented parameters, the description covers purpose and file formats but leaves the operational contract thin. An agent knows roughly what it does but not how to name or safely supply its inputs.

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 description coverage is 0%, so both required parameters are undocumented in the schema. The '[Input: .pdf | Output: .pdf]' note conveys file type but not that the values are paths, whether they may be identical, overwrite policy, or any format constraints.

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 states a specific verb and resource: heuristically detecting text baseline and rotation angle to upright pages. The word 'heuristically' implicitly distinguishes it from an explicit-angle sibling like pdf_rotate, though that contrast is never made explicit.

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?

Usage is only implied: an agent can infer this is for scanned or skewed documents that need automatic correction. There is no explicit when-to-use, no when-not-to-use, and no mention of pdf_rotate as the manual alternative.

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