Skip to main content
Glama

Извлечь страницы

extract_pages

Извлекает выбранные страницы в новый PDF. file_url: публичный URL PDF-файла. pages: список номеров страниц (1-based), порядок сохраняется.

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>",
      "pages": "<pages>"
    },
    "name": "extract_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
pagesYes
file_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is partly covered. The description still adds real value by stating that output goes to a NEW PDF (the source is untouched) and that file_url must be a publicly reachable URL — an access prerequisite not visible in the annotations. It does not cover failure behavior for 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?

Three short blocks with the action stated first, followed by one line per parameter. No filler, and the most decision-relevant information is front-loaded.

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

Completeness4/5

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

For a two-parameter tool with an output schema, the description covers the action, the non-destructive behavior, the access requirement, and both parameters with their edge semantics. Minor gaps remain: behavior on out-of-range or duplicate page numbers, and the output file's naming/location.

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

Parameters5/5

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

Schema coverage is 0%, and the description fully compensates: file_url is documented as a public URL to a PDF, and pages as a 1-based list of page numbers whose order is preserved in the output. The 1-based indexing and order-preservation rules are non-obvious semantics the schema cannot express.

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?

"Извлекает выбранные страницы в новый PDF" names a specific verb (extract) and resource (selected pages into a new file), which distinguishes it in spirit from delete_pages and reorder_pages. It stops short of naming those siblings explicitly, so the differentiation is inferred rather than stated.

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 when-to-use guidance and no routing toward alternatives such as split_pdf (splitting into multiple files) or delete_pages (removing pages rather than keeping them). The agent must infer the use case from the purpose sentence alone.

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.