PDF2MD MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| convert_pdf_to_markdownA | Convert a PDF file to Markdown format using AI sampling. Args: file_path: Local file path or URL to the PDF file output_dir: Optional output directory. Defaults to same directory as input file (for local files) or current working directory (for URLs) Returns: Dictionary containing: - output_file: Path to the generated markdown file - summary: Summary of the conversion task - pages_processed: Number of pages processed |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is singular and clearly defined as converting PDFs to Markdown, leaving no room for misselection.
The single tool name follows a clear verb_noun pattern (convert_pdf_to_markdown), which is consistent with itself. Since there are no other tools, there is no inconsistency to evaluate, making it perfectly consistent by default.
A single tool is too few for most server purposes, as it limits functionality and may indicate an incomplete or overly narrow scope. For a PDF conversion server, one tool is minimal and could benefit from additional related operations, such as batch processing or format validation.
The tool covers the core conversion task well, but there are notable gaps in the surface, such as no tools for handling errors, validating input formats, or managing multiple files. While the main function is present, the lack of supporting operations makes the set incomplete for robust PDF-to-Markdown workflows.