Skip to main content
Glama

pdf_images_to_pdf

Convert JPG, PNG, or WebP image lists into a single PDF file. Provide image paths and an output path to create a PDF from images locally.

Instructions

Converts a list of images to a PDF. [Input: JPG/PNG/WebP images | Output: PDF (.pdf)]

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": {
      "inputs": "<inputs>",
      "output": "<output>"
    },
    "name": "pdf_images_to_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsYesList of image paths.
outputYesThe output PDF file path.

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?

No annotations are supplied, so the description bears the full disclosure burden. It usefully states accepted input formats (JPG/PNG/WebP) and the output type (.pdf), but says nothing about page ordering from the list, behavior on unsupported or missing files, or overwrite behavior for an existing output path.

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 short sentences with the conversion statement front-loaded and the format contract compressed into a bracketed clause. Nothing is redundant and no sentence could be removed without losing information.

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 two-parameter tool with full schema coverage and no output schema, the definition covers the essentials: what goes in, what comes out, and which formats are accepted. Only secondary details (page ordering, overwrite semantics) are absent, which is acceptable at this complexity.

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%, so the schema already documents both parameters, establishing a baseline of 3. The description adds genuine meaning beyond the schema by constraining what the `inputs` strings must be (JPG/PNG/WebP image paths) rather than arbitrary paths.

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 ("Converts a list of images to a PDF") and the emphasis on a list of images implicitly distinguishes it from single-image conversion siblings such as img_to_pdf. It does not name any sibling explicitly, so the differentiation is inferential 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the bracketed input/output summary tells the agent this is an image-to-PDF path, but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g., single image vs. multiple images, or how it relates to img_to_pdf).

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