markdown2pdf-mcp
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 |
|---|---|
| markdown2pdfC | Convert markdown to PDF, and pay with Lightning |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| convert_markdown | Convert markdown to PDF |
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 ambiguity or overlap between tools, as there are no other tools to compare it to. The tool's purpose is clearly defined and distinct by default.
Since there is only one tool, naming consistency is inherently perfect; there are no other tool names to compare it against, so no inconsistencies can exist. The tool name 'markdown2pdf' is straightforward and descriptive.
A single tool is too few for most server purposes, as it limits functionality and suggests an incomplete or overly narrow scope. While the tool is specific to markdown-to-PDF conversion, the server lacks supporting tools for related tasks like previewing, customizing output, or handling errors.
The server is severely incomplete for a markdown-to-PDF domain, as it only provides conversion without essential operations like configuration (e.g., setting page size, fonts), validation, or error handling. This minimal surface will likely cause agent failures when more complex workflows are needed.