Copilot Desktop MCP

by avianhermana

Overview Schema Source Related Servers Discussions Admin

Python

Local

Pdf Merge

pdf_merge

Merge multiple PDF files into one combined document by providing input paths and an output path.

Instructions

Merge multiple PDF files into one combined PDF document.

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": {
      "paths": "<paths>",
      "output_path": "<output_path>"
    },
    "name": "pdf_merge"
  }
}

Input Schema

Name	Required	Description	Default
`paths`	Yes
`overwrite`	No
`output_path`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 10, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden and does not meet it. It says nothing about the critical behavior that the order of the 'paths' array determines page order in the merged output, what 'overwrite' does when the output file exists (fail vs. replace), whether the output directory must pre-exist, or what happens on an invalid/encrypted file.

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?

A single short sentence that is front-loaded with the verb and free of redundant wording. It is efficient, though the brevity here reflects under-specification rather than disciplined economy.

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

Completeness2/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 not be described, but for a 3-parameter mutating file operation with 0% schema coverage and zero annotations the description is far too thin. Merge ordering, overwrite behavior, and failure modes are all unaddressed, leaving the agent to guess at behavior that materially affects the result.

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 the description must compensate for all three parameters and it largely does not. It only implies that 'paths' holds the PDFs and 'output_path' is the destination; it never explains that array order controls merge sequence or what 'overwrite' (default false) changes. This leaves the most consequential semantics undocumented.

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 (merge) and resource (multiple PDF files into one combined PDF), which is unambiguous and naturally distinct from sibling tools like pdf_split or create_pdf. It stops short of explicitly naming a sibling or contrasting use cases, but the action is clear enough that no agent would confuse it.

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, no prerequisites (e.g., that the input files must exist and be valid PDFs), and no mention of when to prefer pdf_split or create_pdf instead. The purpose sentence implies the use case but gives the agent nothing about context, exclusions, or alternative selection.

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

Deploy Server