Skip to main content
Glama

pdf_to_markdown

Convert a PDF file into Markdown text and save it to a specified .md path for editing, publishing, or documentation workflows.

Instructions

Converts a PDF document into Markdown formatted text. [Input: PDF (.pdf) | Output: Markdown (.md)]

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

Input Schema

NameRequiredDescriptionDefault
inputYesThe input PDF file path.
outputYesThe output Markdown 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 supplied, so the description carries the full behavioral burden. It discloses the format contract (PDF in, .md out) but says nothing about scanned/image-only PDFs, password-protected inputs, layout or table fidelity, overwrite behavior when the output path exists, or what happens on failure — all material for a file-mutating conversion tool.

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 compact sentences with the conversion contract front-loaded and a dense format-summary suffix. No filler, though the bracketed notation partially duplicates what the parameter descriptions already say.

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-path conversion tool with a fully documented schema and no output schema, the description covers the essential contract. It is nonetheless thin on the operational caveats (existing output files, unsupported or scanned PDFs) that would let an agent call it confidently without trial and error.

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 100% and both parameters are self-documented as file paths, so the baseline is 3. The bracket notation restates the accepted file types (.pdf input, .md output), which adds only marginal meaning beyond the schema's own descriptions.

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 pair ("Converts a PDF document into Markdown formatted text") with unambiguous direction of conversion. However, it offers nothing to distinguish it from the sibling pdf_convert_markdown, so an agent cannot tell the two apart from the description alone.

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, and no mention of alternatives such as pdf_convert_markdown or office_to_markdown. The agent must infer entirely from the name and the input/output format note when this tool is the right pick.

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