Skip to main content
Glama
Sign In
Paperboy

Paperboy

Official
by sudostash
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

images_to_pdf

DestructiveIdempotent

Combine multiple images into a single PDF, placing each image on its own page in the order provided.

Instructions

Combine images into a single PDF, one image per page, in order.

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_paths": "<input_paths>",
      "output_path": "<output_path>"
    },
    "name": "images_to_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
overwriteNo
input_pathsYes
output_pathYes

Output Schema

NameRequiredDescriptionDefault
pagesYes
outputYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "output": {
+      "title": "Output",
+      "type": "string"
+    },
+    "pages": {
+      "title": "Pages",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "output",
+    "pages"
+  ],
+  "title": "ImagesResult",
+  "type": "object"
+}
  2. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=true, so the safety profile is covered. The description adds ordering and pagination semantics but says nothing about the destructive aspect — notably what happens to a pre-existing file at output_path or how overwrite defaults behave.

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?

A single tight sentence, front-loaded with the action and followed by the two output-shaping details. Nothing is wasted.

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?

For a destructive file-writing tool with an output schema and zero schema documentation, the description should explain overwrite behavior and path expectations; an output schema removes the need to describe return values, but the mutation semantics remain unexplained.

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% across three parameters, so the description carries the full burden and largely fails: it never mentions input_paths format/ordering of the list, output_path expectations, or the overwrite flag's null default. Only the page-ordering behavior is hinted at, which maps loosely to input_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 concrete verb and resource — "Combine images into a single PDF" — plus the meaningful scope detail "one image per page, in order." This separates it from a generic document converter like convert_to_pdf, though it does not name a sibling explicitly.

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 purpose implies when to reach for it (multiple image inputs, PDF output), but there is no explicit when-to-use/when-not guidance, no mention of prerequisites, and no routing to alternatives such as convert_to_pdf for non-image sources.

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