Skip to main content
Glama

pdf_to_html

Convert PDF documents into responsive, styled HTML5 web pages for web viewing and sharing.

Instructions

Converts a PDF document into responsive, styled HTML5 web page.

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_html"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesThe input PDF file path.
outputYesThe output HTML file path.

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 are provided, so the description carries the full burden. It hints at output characteristics (responsive, styled HTML5) but says nothing about whether images/fonts are extracted, fidelity limits, permissions, overwrite behavior on the output path, or failure modes.

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 efficient sentence with the conversion direction front-loaded. No wasted wording, though the brevity is partly the reason behavioral gaps remain.

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 with no output schema and fully documented parameters, the definition is minimally adequate. It is missing behavioral detail an agent would want about output quality and overwrite semantics.

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 description coverage is 100%, with both input and output paths documented in the schema. The description adds no format or constraint detail beyond what the schema already states, so the baseline 3 applies.

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 PDF document into responsive, styled HTML5 web page." That clearly separates it from the reverse-direction sibling html_to_pdf, though it does not address the near-duplicate pdf_convert_html.

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 context, no prerequisites, and no mention of how it differs from the similar pdf_convert_html sibling. The agent must infer selection criteria entirely from names.

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