Skip to main content
Glama

Порядок страниц

reorder_pages

Переупорядочивает страницы PDF. file_url: публичный URL PDF-файла. new_order: новый порядок страниц (1-based). Например [3,1,2] для 3-страничного 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": {
      "file_url": "<file_url>",
      "new_order": "<new_order>"
    },
    "name": "reorder_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_urlYes
new_orderYes

Output Schema

NameRequiredDescriptionDefault

No arguments

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?

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description contributes the meaningful constraint that file_url must be a public URL, but says nothing about whether the result is a new file or an in-place modification, nor about rate limits or failure modes.

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?

Three short lines: the operation first, then each parameter on its own line with a clarifying example. No 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.

Completeness3/5

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

For a two-parameter mutation tool with an output schema present, return values need not be explained, and annotations cover the safety profile. However, the description never states whether the operation returns a new file or overwrites, nor what happens if new_order omits pages, leaving a behavioral gap for a write operation.

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?

With 0% schema coverage, the description carries the full burden and does so effectively: file_url is identified as a public URL, and new_order is explained as a 1-based ordering with the concrete example [3,1,2] for a 3-page PDF, which implies a full permutation. It stops short of stating whether new_order must cover every page, which is the one remaining ambiguity.

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 opens with a specific verb+resource ("Переупорядочивает страницы PDF"), which unambiguously identifies the operation. It does not name distinguishing siblings such as delete_pages or extract_pages, but the action itself is distinct enough that confusion is unlikely.

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 explicit guidance on when to use this tool versus alternatives (rotate_pdf, extract_pages, merge_pdfs) and no stated preconditions beyond the implied URL requirement. The agent must infer usage context purely from the tool name.

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.