readdown-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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_markdownA | Fetch a web page and convert it to clean, LLM-optimized Markdown. Returns the article content with metadata (title, author, date) and token count. Much faster and lighter than browser-based solutions. |
| convert_htmlA | Convert an HTML string to clean, LLM-optimized Markdown. Use this when you already have HTML content and need it as Markdown. |
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 2 tools
The two tools have clearly distinct purposes: convert_html processes existing HTML strings, while fetch_markdown retrieves and processes web pages. There is no overlap in functionality, making tool selection straightforward for an agent.
Both tools follow a consistent verb_noun pattern (convert_html and fetch_markdown), using clear action verbs that describe their operations. The naming is predictable and aligned with their functions.
With only two tools, the server feels minimal for a web content processing domain. While the tools cover core use cases, the scope is thin, potentially limiting agent workflows without additional operations like batch processing or format validation.
The tools provide essential coverage for converting HTML to Markdown, both from strings and web pages. However, there are minor gaps, such as no tool for reverse conversion (Markdown to HTML) or handling specific HTML elements, which agents might need to work around.