Skip to main content
Glama

pdf_to_epub

Convert fixed-layout PDF documents into reflowable EPUB 3.0 eBooks for flexible reading on e-readers and mobile devices.

Instructions

PDF to EPUB 3.0: Convert fixed-layout PDF documents into reflowable EPUB 3.0 eBooks [Input: .PDF | Output: ..EPUB]

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": "<input>",
      "output": "<output>"
    },
    "name": "pdf_to_epub"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
outputYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations, so the description carries the full behavioral burden; it only states conversion direction and formats. It says nothing about fidelity risks (reflow may lose tables, images, layout), whether the output file is overwritten, or whether the call is synchronous or may fail on malformed input.

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?

A single front-loaded sentence with the format pair appended; no wasted words. The '[Input | Output]' fragment is slightly cryptic but efficiently conveys the core contract.

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?

For a simple two-parameter conversion tool with no annotations and no output schema, the definition covers the basic transformation but leaves the response shape (output file path? success flag?) and failure behavior unexplained.

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 0%, so the description must compensate. The stated formats ([Input: .PDF | Output: .EPUB]) loosely map to the two required parameters, but it does not clarify whether they are file paths, whether the output path must exist or be creatable, or how errors surface.

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: convert fixed-layout PDFs into reflowable EPUB 3.0 eBooks. The format pair makes it distinguishable from siblings like pdf_to_docx or pdf_to_html, though it never explicitly names them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites (e.g., must be a fixed-layout PDF; scanned PDFs need OCR first), and no mention of alternative converters in the large sibling set.

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