Convert any URL into clean, token-efficient Markdown for LLMs. One thing, done well.
Single tool with clear naming (url_to_markdown), good description (194 chars, within baseline 34-392), and complete input schema with types and descriptions. Parameters are well-constrained (booleans with defaults). However, output schema is not documented in the MCP registration, only described in prose. No error handling guidance for common failures (network timeouts, unsupported content types, extraction failures). Tool is read-only and idempotent, which is good, but these properties are not explicitly annotated.
Convert any web page URL to clean, token-efficient Markdown. Returns the main content of the page (headings, text, tables, lists, code blocks, image alt text) with navigation, ads and other boilerplate removed. Set include_links=false to also drop link URLs and save tokens. Set render=true to force JavaScript rendering, e.g. when the result misses content that the page loads client-side.
Output schema not documented. Tool description mentions return structure (headings, text, tables, lists, code blocks, image alt text) but MCP tool definition lacks explicit output schema. LLMs cannot plan downstream operations without knowing the exact response structure.
No error handling guidance. Tool can fail with network timeouts, unsupported content types, extraction errors, and JavaScript rendering failures. Descriptions do not explain what errors are retryable, what the LLM should do on failure, or how to recover.
Tool annotations missing. Tool is read-only and idempotent but does not declare readOnlyHint or idempotentHint in the MCP schema. This prevents clients from optimizing caching and retry logic.
Parameter 'render' uses string enum ('auto', 'never', 'force') but schema does not declare enum constraint. LLMs may hallucinate invalid values like 'always' or 'on-demand'.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 58 | 2026-07-28+ | v2 |
STDIO transport only. Server is not remotely accessible and cannot be used by hosted MCP clients. Limits deployment to local/CLI-only scenarios.