Skip to main content
Glama
Sign In
Paperboy

Paperboy

Official
by sudostash
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

convert_to_pdf

DestructiveIdempotent

Create PDFs from images, text/markdown files, or Office/HTML documents; Office/HTML conversion requires LibreOffice installed.

Instructions

Create a PDF from an image, a text/markdown file, or an Office/HTML document.

Office/HTML (docx, xlsx, pptx, odt, html, ...) requires LibreOffice installed.

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_path": "<input_path>"
    },
    "name": "convert_to_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
overwriteNo
input_pathYes
output_pathNo

Output Schema

NameRequiredDescriptionDefault
pagesYes
outputYes
source_kindYes

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"
+    },
+    "source_kind": {
+      "enum": [
+        "image",
+        "text",
+        "office"
+      ],
+      "title": "Source Kind",
+      "type": "string"
+    }
+  },
+  "required": [
+    "output",
+    "pages",
+    "source_kind"
+  ],
+  "title": "ConvertResult",
+  "type": "object"
+}
  2. First observedv0.1.0

TDQS

B3.4/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 structurally. The description's genuine contribution is the external LibreOffice dependency for Office/HTML inputs, which annotations cannot express. It does not, however, disclose what the destructiveHint actually threatens — e.g. that an existing file at output_path may be clobbered when 'overwrite' is set — nor where a PDF lands when output_path is omitted.

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?

Two sentences, the primary action stated first and the conditional dependency second — no filler. The structure is efficient, though the requirement line could be tied more tightly to the input-type sentence it qualifies.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Placeholder for the sixth dimension score computed above.

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 must compensate and largely fails to. It explains what kinds of input_path values are acceptable, but 'overwrite' and 'output_path' are never mentioned, leaving their semantics and defaults entirely 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 opens with a specific verb and resource ('Create a PDF from…') and enumerates the supported source types (image, text/markdown, Office/HTML), which lets an agent distinguish it from siblings like pdf_to_markdown or extract_pages. It does not explicitly contrast itself with the near-neighbor convert_to_pdfa or with images_to_pdf, so the differentiation is implicit 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?

It supplies one concrete prerequisite ('Office/HTML … requires LibreOffice installed'), which is a real gating condition an agent must know. Beyond that there is no when-to-use vs. when-not-to-use guidance and no pointer to the sibling that handles PDF/A conversion or the image-only variant, so usage is implied from the input-type list rather than spelled out.

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