Skip to main content
Glama
Sign In
Distill MCP server

Distill MCP server

by Bytestay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

fetch_markdown

Read-onlyIdempotent

Fetches a web page and converts its main content into Markdown with title, author, date, language, and clear status reasons when content cannot be retrieved.

Instructions

Fetch a web page and return its main content as Markdown, with title, author, date and language.

status is "ok" on success. Other values (robots_txt, opted_out, blocked, not_html, http_error, unreachable) explain why there is 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": {
      "url": "<url>"
    },
    "name": "fetch_markdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPage to fetch (http or https).
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.4

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover readOnly, openWorld, idempotent and non-destructive, so the safety profile is cheap. The description still adds real value by enumerating the status outcomes (robots_txt, opted_out, blocked, not_html, http_error, unreachable), telling the agent this tool fails gracefully with a reason rather than throwing. It does not mention truncation behavior or that content may be cut by max_chars.

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 tight sentences with the return shape front-loaded and the status semantics second. Every clause carries information an agent needs; nothing is redundant with the name or annotations.

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?

With no output schema, the description carries the return contract and does so: content as Markdown, title/author/date/language metadata, and a full status vocabulary for the no-content cases. That is enough for an agent to interpret any response without guessing.

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% and each parameter is documented there, so baseline 3 applies. The description adds no parameter-level meaning beyond the schema, such as how include_links affects the returned link list or what happens to tables when disabled.

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 ('Fetch a web page') and names the output form ('main content as Markdown') plus returned metadata. It implicitly distinguishes from html_to_markdown by starting from a URL rather than existing HTML, but never names that sibling 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 only implied: an agent infers you call this when you have a URL and want readable content. There is no explicit when-to-use framing, no mention of when to prefer html_to_markdown, and no prerequisites (network access, allowed domains) 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