html_to_markdown
Convert HTML to clean Markdown. Returns: {markdown, original_length, markdown_length}
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| html | Yes |
Htmlpdf Transform Mcp
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3.3/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavioral traits. It mentions the return format ({markdown, original_length, markdown_length}), which adds some transparency, but lacks details on limitations, error handling, or input constraints.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is short and front-loaded with the main purpose. It is efficient, though it could include more information without becoming verbose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (one parameter, no output schema), the description is partially complete. It covers purpose and return structure but lacks usage guidelines and behavioral details.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 0% description coverage and the description does not elaborate on the 'html' parameter beyond its existence. No format, size limits, or examples are given.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool converts HTML to clean Markdown, which is a specific verb and resource. It distinguishes from sibling tools like 'extract_tables_from_html' and 'html_to_text'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives. The description does not mention when not to use or provide context for selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
B3.3/5.0
Disambiguation5/5
Each tool has a clearly distinct purpose: extracting tables, health check, converting HTML to markdown or text, and converting JSON to markdown table. No functional overlap.
Naming Consistency4/5
Most tools follow a pattern (source_to_target or verb_noun), and all use snake_case. One exception: 'health_check' is a noun_noun instead of verb_noun, but it's a minor deviation.
Tool Count4/5
With 5 tools, the count is reasonable for a focused server. It covers core HTML transformations, though PDF tools are missing from the name 'Htmlpdf'.
Completeness2/5
The server name implies both HTML and PDF handling, but there are no PDF-related tools. Significant gaps exist in the stated domain, limiting agents' ability to perform PDF operations.