ScorpTech x402 Tools

Markdown To Html

markdown_to_html

Read-onlyIdempotent

Render Markdown to safe HTML: CommonMark-style blocks (ATX / setext headings, paragraphs, block quotes, nested ordered / bullet lists, fenced and indented code with language classes, thematic breaks) and inlines (emphasis, strong, code spans, links, images, reference links, autolinks, hard breaks, escapes, entities) plus GitHub extensions (tables with alignment, task lists, strikethrough, bare URL autolinks). Raw HTML is escaped by default or allowlist-sanitized; javascript: and other unsafe URLs are dropped. Returns HTML, heading ids and a table of contents. Offline, deterministic. Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/markdown-to-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

Name	Required	Description	Default
`breaks`	No	Treat single newlines as <br>
`markdown`	Yes	Markdown source
`allowHtml`	No	Keep raw HTML (sanitised with an allowlist) instead of escaping it
`headingIds`	No	Add GitHub-style id slugs to headings
`linkTarget`	No	Open links in a new tab (adds rel=noopener noreferrer)	none

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Beyond the annotations, the description discloses important behavior: raw HTML is escaped by default or allowlist-sanitized, unsafe javascript: URLs are dropped, output includes HTML, heading ids, and a table of contents, and the operation is offline and deterministic. The price and HTTPS endpoint add further useful operational context.

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?

The description is front-loaded with the core purpose and remains focused on relevant conversion behavior. It is somewhat dense and feature-list heavy, but the detail is relevant for a Markdown renderer and does not contain obvious waste.

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?

With no output schema, the description adequately states that the tool returns HTML, heading ids, and a table of contents, and it covers safety, determinism, and pricing. It could be more precise about the output structure or TOC shape, but it is complete enough for an agent to invoke the tool 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%, so all five parameters are already documented clearly. The description reinforces the allowHtml and headingIds behavior but does not add syntax or semantics for breaks or linkTarget beyond the schema, so the 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?

The description states a specific verb and resource: 'Render Markdown to safe HTML.' It further distinguishes the tool's scope by enumerating supported CommonMark and GitHub Markdown features, raw HTML handling, and returned artifacts, making it clearly different from siblings like html_to_markdown or markdown_table.

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 description makes the conversion use case clear, including safety defaults and supported syntax, but it does not explicitly say when to choose this tool over alternatives such as html_to_markdown or markdown_table. Usage is therefore implied rather than routed.

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

All ScorpTech x402 Tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?