Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

web_dev_markdown_to_html

Read-onlyIdempotent

Convert Markdown to HTML for web display. Uses regex to parse headings, bold, italic, code, lists, tables, blockquotes, and links. Returns rendered HTML and stats.

Instructions

Markdown to HTML Converter. Convert Markdown text into HTML using fast regex-based rules: ATX headings (h1-h5), bold/italic/bold-italic, strikethrough, inline code and fenced code blocks (with language class), links, images, ordered and unordered lists, blockquotes, horizontal rules, GFM pipe tables, and paragraphs. Use this to render Markdown for display; use web_dev_html_to_markdown for the inverse (HTML to Markdown), and webdev_html_minifier to shrink HTML rather than generate it. Runs locally on the input you provide: read-only, non-destructive, deterministic, offline, contacts no external service, and is rate-limited (anonymous 60 req/min, 500/hr). Returns the rendered HTML, a stats object counting produced elements, and a sanitised preview HTML with disallowed tags stripped. Note: the three options are accepted for forward compatibility but do not currently change the output.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
markdownYesThe Markdown source to convert. Required and must be non-empty, or a 400 is returned.
optionsNoReserved options. Currently accepted but ignored; output is identical whether or not they are set.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
htmlNoThe rendered HTML output.
statsNoCounts derived from the input Markdown and resulting HTML.
preview_safeNoCopy of the HTML with tags outside an allow-list stripped, safe for preview.
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond annotations (readOnlyHint, destructiveHint, idempotentHint), description adds critical details: runs locally, deterministic, offline, rate-limited (60 req/min, 500/hr), non-destructive, and describes return structure (rendered HTML, stats, sanitized preview). Also clarifies that options are currently ignored. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is well-structured, front-loaded with purpose, then features, usage guidance, properties, return info. No redundant sentences; every sentence provides essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (one required param, optional options, output schema exists), the description covers input constraints, behavior, return values, rate limits, and forward compatibility. Fully complete for agent selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds value beyond schema: for markdown, notes non-empty requirement and 400 error; for options, states they are reserved and do not change output. This extra context justifies a score above baseline 3.

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 Markdown to HTML using regex-based rules, listing supported elements (headings, bold, code, tables, etc.). It differentiates from siblings by naming the inverse tool (web_dev_html_to_markdown) and the minifier (webdev_html_minifier), providing specific verb+resource scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use ('render Markdown for display') and explicitly names alternatives for inverse conversion and HTML minification. Provides clear context for choosing this tool over siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server