Skip to main content
Glama

Caelara Labs Document Utilities

markdown_to_sanitized_html

Render markdown to HTML with all raw HTML escaped and unsafe URLs removed

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

Input Schema

NameRequiredDescriptionDefault
markdownYesMarkdown text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the two behaviors that matter for a sanitizer: raw HTML is escaped and unsafe URLs are stripped. It stops short of defining what counts as an unsafe URL scheme or whether the operation is lossless/idempotent, so the safety contract is stated but not fully specified.

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?

A single sentence with the transformation front-loaded and the two safety qualifiers trailing as modifiers. No filler, nothing redundant with the schema.

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 pure transformation with no output schema, the description gives enough to call it correctly and to know the output is sanitized HTML. A note on the markdown dialect accepted and the exact return type would close the remaining gap.

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 one parameter and schema coverage is 100%, so the schema already documents "markdown" adequately. The description adds nothing about input format (GFM vs CommonMark, tables, code fences), so the baseline 3 applies.

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?

The description pairs a specific verb ("Render") with a precise transformation (markdown to HTML) and adds two qualifiers (raw HTML escaped, unsafe URLs removed). Directionality is unambiguous and clearly the inverse of the html_to_clean_text sibling, but no sibling is named explicitly.

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?

Usage is implied rather than stated: an agent can infer this is the tool for turning markdown into safe HTML. There is no explicit when-to-use/when-not guidance and no mention of which alternative to pick if the input is already HTML or if sanitization is unwanted.

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