Skip to main content
Glama

Convert Markdown to HTML with headings and links

markdown
Read-only

Markdown to HTML with GitHub-flavoured tables and strikethrough, heading ids, the list of headings and links, and a word count. Raw HTML in the input is escaped unless allowHtml is true; links and images with javascript:, vbscript: or data: addresses are removed. Pure code, no outbound request. Input up to 200 KB. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "markdown": "<markdown>"
    },
    "name": "markdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
gfmNoGitHub-flavoured Markdown, default true
markdownYesThe Markdown text, up to 200 KB
allowHtmlNoKeep raw HTML from the input, default false (escaped)
headingIdsNoGive each heading an id, default true

Output Schema

NameRequiredDescriptionDefault
htmlNo
linksNo
sourceNo
optionsNo
headingsNo
checkedAtNo
wordCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the supplied annotations by disclosing the escaping policy (raw HTML escaped unless allowHtml), the URL sanitization rules (javascript:, vbscript:, data: links/images removed), the 200 KB input ceiling, and the billing model including the fact that failed calls are free. readOnlyHint=true is consistent with the described pure-computation behavior; 'no outbound request' clarifies that input URLs are never fetched, which is meaningful context for an agent handling untrusted Markdown.

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?

Front-loaded with the core conversion and output features, followed by security, limits, and billing in a logical order, with zero filler sentences. It is a dense single paragraph that packs several distinct concerns together, which is efficient but slightly heavy to scan.

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?

With an output schema present, return values need not be explained, and the description still names the secondary outputs (headings, links, word count). Input constraints, sanitization behavior, and payment requirements are all covered, leaving nothing an agent needs in order to call it correctly.

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

Parameters3/5

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

Schema description coverage is 100% and each of the four properties already documents its effect and default, so the schema does the heavy lifting. The description only reinforces one of them (allowHtml) and implies the 200 KB limit on markdown; it adds no meaning beyond the schema, which is the expected baseline here.

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?

States a concrete transformation (Markdown to HTML) and enumerates the exact output features the agent will get: GFM tables, strikethrough, heading ids, extracted headings/links lists, and a word count. That level of specificity lets an agent predict the result without opening the schema, and none of the listed siblings (links, tables, classify, etc.) overlap with a Markdown converter.

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

Usage Guidelines3/5

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

The feature list implicitly tells the agent this is the tool for rendering Markdown, and the 'Pure code, no outbound request' line hints it is safe for untrusted input. However, there is no explicit when-to-use / when-not-to-use statement and no routing away from any alternative, so guidance is inferred rather than stated.

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.

Resources