Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_docs_markdown_to_sanitized_html

Converts Markdown into sanitized HTML by escaping raw HTML and removing unsafe URLs, helping produce safer rendered documents.

Instructions

[Document Utilities] Render markdown to HTML with all raw HTML escaped and unsafe URLs removed Measured p50 10 ms, p95 14 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://docs.caelaralabs.com.

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": "caelara_docs_markdown_to_sanitized_html"
  }
}

Input Schema

NameRequiredDescriptionDefault
markdownYesMarkdown text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose real behavioral traits: escaped raw HTML, stripped unsafe URLs, and measured p50/p95 latency plus the backing service endpoint. It still does not say what the return payload looks like or how malformed markdown is handled, which keeps it from a 5.

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?

One sentence, front-loaded with the category tag and the core verb+resource, followed by the distinguishing sanitization detail and then the supplementary performance data. Nothing is redundant and the operative information arrives first.

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

Completeness4/5

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

For a one-parameter converter with no output schema, the definition covers behavior, security guarantees, and latency, which is close to sufficient. The notable gap is the shape of the response (HTML string vs. wrapped object) and error behavior, which an agent cannot derive from the absent output schema.

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?

There is a single required parameter whose schema description coverage is 100%, so the schema already documents 'markdown' as 'Markdown text'. The description adds no syntax, size limits, or format constraints beyond that, which is the expected baseline when the schema does the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and transformation: render markdown to HTML, with the added qualifiers that raw HTML is escaped and unsafe URLs removed, which precisely characterizes output beyond a generic converter. It does not name a sibling such as caelara_docs_html_to_clean_text, so an agent must infer the division of labor, keeping this below a 5.

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 sanitization guarantee ('all raw HTML escaped and unsafe URLs removed') implicitly signals the when-to-use case: untrusted or user-supplied markdown needing safe rendering. However, there is no explicit guidance on when not to use it, no mention of alternatives like the reverse html_to_clean_text sibling, and no prerequisites stated.

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

Deploy Server

Other Tools