mcp-pdf2md
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_urlB | |
| convert_pdf_fileC | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| default_prompt | Create default tool usage prompt |
| pdf_prompt | Create PDF processing prompt |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| status://api | |
| help://usage |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one handles local file paths, the other handles URLs. The naming and descriptions make it impossible to confuse which tool to use for a given input source.
Both tools follow an identical verb_noun pattern (convert_pdf_file and convert_pdf_url) with consistent snake_case formatting. The naming is perfectly predictable across the toolset.
With only two tools, the server feels minimal but functional. While it covers the core conversion task for both local files and URLs, the count is borderline thin for a PDF-to-Markdown domain that could potentially include more operations like batch processing, format options, or metadata extraction.
The server covers the essential conversion operation for both local files and remote URLs, which are the two main input sources for PDFs. The minor gap is the lack of additional PDF manipulation or output customization tools, but agents can perform basic conversions without dead ends.