Hopi

Markdown previewer

hopi_markdown_previewer

Read-onlyIdempotent

Render a small, safe subset of markdown to HTML: headings (# to ###), bold, italic, links (http, https or mailto only), inline code, fenced code blocks, bulleted and numbered lists, and blockquotes. Every character is HTML-escaped first, so raw HTML is shown as text and never executed. Source: https://hopi.co.uk/markdown-previewer/

Input Schema

TableJSON Schema

Name	Required	Description	Default
`markdown`	Yes	The markdown source to render

Output Schema

TableJSON Schema

Name	Required	Description
`html`	No
`summary`	Yes
`source_url`	Yes	The tool's page on hopi.co.uk (cite or open to check the figure)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026
- addedOutput schema / required
```
Added value: +[
+  "source_url",
+  "summary"
+]
```
First observedSep 20, 2026

TDQS

A4.4/5.0

Behavior5/5

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

It discloses the key behavioral constraint: the supported markdown subset, allowed link schemes, and the HTML-escaping guarantee that raw HTML is never executed. This adds real safety-relevant context beyond the readOnly/idempotent/destructive annotations.

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 definition is compact and front-loaded: purpose first, supported subset next, safety behavior after, then a source URL. The URL is of marginal value for tool invocation but does not obscure the essential guidance.

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?

Given the single string parameter, full schema coverage, a provided output schema, and complete safety annotations, the description covers everything an agent needs to call the tool correctly. It also handles the edge case of raw HTML input explicitly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning by listing the accepted markdown constructs and restricting link protocols to http, https, and mailto. This tells an agent what input characteristics are honored.

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 opens with a specific verb and resource ('Render ... markdown to HTML') and enumerates exactly which markdown constructs are supported. It clearly distinguishes this tool from text-utility siblings like hopi_html_escape by framing it as a previewer rather than an encoder/decoder.

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 intended use is clear from the purpose, but the description never states when to choose this over alternatives or when it would be inappropriate (e.g., full CommonMark rendering). Usage guidance remains implied rather than explicit.

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

All Hopi 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?