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

pdf-toolkit-mcp

by EigenCharlie
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

image_to_pdf

Combine multiple images into a single PDF, with each image on a separate page in the order provided.

Instructions

Combine one or more images (.jpg, .jpeg, .png) into a single PDF, one image per page, in the order provided.

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": "image_to_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_filesYesOne or more image files (.jpg, .jpeg, .png), in the order they should appear in the PDF.
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

A4/5.0
Behavior3/5

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

With no annotations, the description adds some behavioral context: output path behavior (optional, defaults to first input's directory). However, it does not disclose error handling (e.g., invalid files), overwrite behavior, or required permissions.

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?

The description is a single, well-structured sentence that front-loads the main purpose and includes key details without redundancy. Every word earns its place.

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 simple tool with 2 parameters and no output schema, the description covers purpose, input format, ordering, and output behavior. It lacks details on error handling or invalid inputs but is otherwise sufficient.

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?

Schema coverage is 100%, but the description adds value by explicitly listing supported image formats (.jpg, .jpeg, .png), which are not mentioned in the input_files schema description. This is crucial for correct usage.

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 tool combines one or more images into a single PDF, one per page, in order. It specifies supported formats (.jpg, .jpeg, .png) and distinguishes from sibling PDF tools like pdf_to_jpg or ocr_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 creating PDFs from images but does not provide explicit guidance on when to use this tool versus alternatives (e.g., office_to_pdf, html_to_pdf). No exclusions or when-not-to-use scenarios are mentioned.

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