Skip to main content
Glama
Sign In
pdf-toolkit-mcp

pdf-toolkit-mcp

by EigenCharlie
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

merge_pdf

Combine multiple PDF files into one document while maintaining their original order.

Instructions

Merge two or more PDF files into a single PDF, preserving order. Outputs a .pdf file on disk and returns its path.

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": {
      "input_files": "<input_files>"
    },
    "name": "merge_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_filesYesTwo or more PDF files to merge, in order.
output_pathNoOptional output path. If it ends with the expected extension, the file is written there. If it is a directory, the file is placed inside with a timestamped name. Defaults to the same directory as the first input.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description discloses key behaviors: order preservation, output as .pdf file on disk, and return of file path. It does not cover edge cases or error handling, but is adequate for a simple tool.

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?

Two sentences with no fluff. First sentence states the core action, second adds output details. Highly efficient.

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?

Lacks details on output_path behavior (directory vs file), error handling, or file existence handling. No output schema, so description should cover return value—it does, but incompletely. Moderate completeness.

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 coverage is 100% as both parameters have descriptions. The description adds minimal value beyond the schema (only mentions order preservation and output format). Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb (Merge), resource (PDF files), and action (into a single PDF, preserving order). It distinguishes well from sibling tools like split_pdf or compress_pdf.

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?

The description implies usage for merging multiple PDFs in order but provides no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites.

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

Deploy Server

Other Tools