Skip to main content
Glama
Sign In
Distill MCP server

Distill MCP server

by hybridforgelab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

html_to_markdown

Read-onlyIdempotent

Convert raw HTML you already have into clean, main-content Markdown without fetching pages; optionally keep links, images, and tables while honoring noai directives.

Instructions

Turn HTML you already have into clean Markdown (main content only). A noai directive in the HTML is honoured: the result then has no content.

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": {
      "html": "<html>"
    },
    "name": "html_to_markdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
htmlYesRaw HTML you already have (up to 5 MB). Nothing is fetched.
base_urlNoPage URL, to resolve relative links and images.
max_charsNoCut the Markdown to this many characters.
include_linksNoKeep links and return the list of links.
include_imagesNoKeep images as ![alt](src).
include_tablesNoKeep tables as Markdown tables.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real behavioral context beyond them: extraction is limited to main content, and a `noai` directive yields an empty result — a non-obvious edge case an agent would otherwise misread as failure.

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?

Two short sentences, front-loaded with the action and scope, then the noai edge case. Nothing is redundant and no sentence could be removed without losing information.

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 six-parameter conversion tool with full schema coverage and annotations covering safety, the description covers purpose, scope and the key gotcha. It does not mention the returned links list or the truncation behavior of max_chars, a minor gap given there is no 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?

Schema description coverage is 100%, so every parameter including html, base_url, max_chars and the include_* flags is already documented in the schema. The description adds no syntax or format detail on top, 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?

States a specific verb and resource ('Turn HTML ... into clean Markdown') plus a scope qualifier ('main content only'). The phrase 'HTML you already have' implicitly separates it from the sibling fetch_markdown, which fetches; it does not name that sibling, so it stops short of 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?

Usage is implied by 'HTML you already have' and the schema note 'Nothing is fetched', which hints at the alternative fetch_markdown for remote pages. There is no explicit when-to-use/when-not statement or named alternative, so guidance is only inferable.

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