Skip to main content
Glama

Объединить PDF

merge_pdfs

Объединяет несколько PDF в один. Порядок файлов = порядок страниц. file_urls: список публичных URL PDF-файлов (минимум 2).

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_urls": "<file_urls>"
    },
    "name": "merge_pdfs"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_urlsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavior beyond that: output page order follows input file order. It does not say what happens on a failed/unreachable URL or whether the result is stored/returned, which matters for a non-idempotent merge.

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 sentences, zero filler, with the core action front-loaded and the ordering rule and parameter constraint following in priority order. Nothing redundant.

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?

An output schema exists, so return values need no explanation, and the tool has only one parameter. The remaining gap is edge-case behavior (invalid/unreachable URL, maximum number of files) for a non-idempotent operation that depends on external public URLs.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must carry the load; it does document the single parameter as an ordered list of public PDF URLs with a minimum of two entries, which is real added meaning. It stops short of stating format requirements (https, size limits, max count), so it partially rather than fully compensates.

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?

States a specific verb and resource: 'Объединяет несколько PDF в один' (merges several PDFs into one). It is clearly distinguishable from the many conversion and page-manipulation siblings (split_pdf, extract_pages, reorder_pages), though it never names a sibling explicitly to reinforce the boundary.

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 implied by the purpose itself and the 'minimum 2 files' constraint signals when the tool applies. However, there is no guidance on when to prefer this over extract_pages/split_pdf, no prerequisites about source files, and no mention of limits.

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.