markdown-to-html
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 |
|---|---|
| markdown_to_htmlC | Convert Markdown to HTML |
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 ambiguity or overlap between tools. The tool's purpose is clearly defined as converting Markdown to HTML, making it impossible for an agent to misselect among multiple options.
The single tool name 'markdown_to_html' uses a consistent snake_case pattern and follows a clear verb_noun structure (convert_markdown_to_html implied). Since there is only one tool, there is no inconsistency to evaluate, and the naming is straightforward and appropriate.
A single tool for a server named 'markdown-to-html' feels thin and under-scoped. While the tool directly addresses the core function, typical MCP servers in this domain might include additional tools for validation, configuration, or handling different Markdown flavors, making this count borderline minimal for practical use.
The tool covers the basic conversion from Markdown to HTML, which aligns with the server's stated purpose. However, there are notable gaps, such as lack of tools for HTML to Markdown conversion, validation, or customization options, which could limit agent functionality in more complex scenarios.