Skip to main content
Glama

Text Analysis & Cleanup Tools (Tanod)

markdown_to_html

Read-onlyIdempotent

utilpeek: Convert Markdown to sanitized HTML. For the reverse use html_to_text. Returns the HTML of a Markdown document (markdown-it-py; gfm adds tables, strikethrough, autolinks and task lists), cleaned by an allow-list sanitizer (nh3): no scripts, event handlers, iframes, forms or javascript:/data: links; every link gets rel="nofollow noopener noreferrer". HTML over 4 MB is a 422 output_too_large. Parsed in an isolated, resource-limited child process without network; input over its limits is a 422 (not charged). Typically under 0.5 s. Price: USD 0.001. Free: 10 utilpeek calls per IP per UTC day. Docs: https://tanod.dev/learn/markdown-to-html-api.html

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_to_html"
  }
}

Input Schema

NameRequiredDescriptionDefault
flavorNogfm (default) adds tables, strikethrough, autolinks and task lists.gfm
markdownYesMarkdown source (at most 200,000 characters).

Output Schema

NameRequiredDescriptionDefault
htmlNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
flavorNo
sourceNo
sanitizedNo
html_charsNo
removed_by_sanitizerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / flavor / title
      Removed value: -"Flavor"
    • removedInput schema / properties / markdown / title
      Removed value: -"Markdown"
    • removedInput schema / title
      Removed value: -"markdown_to_htmlArguments"
    • removedOutput schema / properties / source / properties
      Removed value: -{
      -  "library": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "license": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  }
      -}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "error": {
      +      "description": "Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object."
      +    },
      +    "flavor": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "html": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "html_chars": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "removed_by_sanitizer": {
      +      "type": [
      +        "boolean",
      +        "null"
      +      ]
      +    },
      +    "sanitized": {
      +      "type": [
      +        "boolean",
      +        "null"
      +      ]
      +    },
      +    "source": {
      +      "properties": {
      +        "library": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "license": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        }
      +      },
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses the allow-list sanitizer behavior (no scripts/event handlers/iframes/forms/javascript: links, rel="nofollow noopener noreferrer" on links), the 4 MB output cap returning 422 output_too_large, isolated no-network child-process execution, input-limit 422s that are not charged, typical latency, price, and free-tier quota. These are exactly the operational facts an agent needs before calling a conversion tool.

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 purpose and the reverse-direction pointer, then progressively more operational detail. It is a dense run-on paragraph with pricing/docs links appended, but nearly every clause carries usable information; only the markdown-it-py/nh3 library names are arguably incidental.

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?

Covers conversion semantics, sanitization guarantees, size limits and error codes, execution isolation, latency, and cost — everything needed to call it correctly for a two-parameter tool. An output schema exists and the description still adds helpful output characteristics (sanitization, 4 MB cap) without wasting space explaining return structure.

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 coverage is 100%, so both parameters (markdown, flavor) are already documented, including the enum and the gfm explanation. The description largely restates the gfm additions rather than adding new parameter-level meaning (e.g. it does not say which character classes or inputs are rejected before parsing). Baseline 3 is appropriate.

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 specific verb+resource ('Convert Markdown to sanitized HTML') with the output property (sanitized) baked in, and explicitly names the sibling html_to_text as the reverse operation. An agent can distinguish it from convert_markdown_to_word or convert_document_to_markdown without opening any schema.

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

Usage Guidelines4/5

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

Names the alternative for the opposite direction ('For the reverse use html_to_text') and implies usage context via the sanitizer/limits framing. It does not explicitly contrast with other markdown-output siblings (e.g. convert_markdown_to_word), but the guidance given is clear and actionable.

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.