Skip to main content
Glama

Повернуть страницы

rotate_pdf

Поворачивает страницы PDF. file_url: публичный URL PDF-файла. pages: список номеров страниц (1-based) или "all" для всех. angle: угол поворота: 90 | 180 | 270.

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": {
      "file_url": "<file_url>"
    },
    "name": "rotate_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
angleNo
pagesNoall
file_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds no behavioral context at all — it does not say whether the original file is modified or a new file is returned, what happens with out-of-range page numbers, or anything about the open-world network dependency. With annotations present the bar is lower, but zero added context keeps this at 2.

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?

One purpose sentence followed by a compact three-line parameter glossary; the purpose is front-loaded and every line carries information the schema itself lacks. No filler or repetition.

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?

The tool is a simple three-parameter mutation, and an output schema exists so return values need not be explained. However, the description never states whether the input file is transformed in place or a new file is produced, which is the key thing an agent needs to chain this tool with others.

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 description coverage is 0%, so the description carries the full burden, and it does well: it explains that file_url must be a public URL, that pages is a 1-based list or the string "all", and that angle is restricted to 90 | 180 | 270. Only edge cases (invalid page numbers, non-listed angles) are unaddressed.

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 opening line 'Поворачивает страницы PDF' gives a specific verb and resource, so an agent immediately knows this rotates pages in a PDF rather than an image. It does not explicitly distinguish itself from the sibling rotate_image, which is the only real ambiguity.

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 guidance on when to choose this over rotate_image or reorder_pages, and no statement about prerequisites beyond 'file_url is a public URL'. The agent is left to infer appropriate usage entirely from the name and parameters.

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.