Skip to main content
Glama
Sign In
Docling-rs MCP

Docling-rs MCP

Official
by docling-project
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

convert_to_markdown

Read-only

Read a document and return its Markdown text, with support for PDFs (layout, tables, OCR), Word, PowerPoint, Excel, HTML, EPUB, email, images, and audio. Use when Markdown is all you need.

Instructions

Read a document as Markdown, with default settings, and return the Markdown text. Handles PDF (layout analysis, tables, OCR for scans), Word, PowerPoint, Excel, HTML, EPUB, e-mail, images, audio and more. Use this whenever Markdown is all you need. Use convert instead for another output format (docling JSON, HTML, RAG chunks, …), embedded images, or options such as a page range, OCR language or password. Fails with a message when the document is missing, outside the server's root, of an unsupported type (see list_input_formats), or a URL while URL fetching is off. Read-only. Same name and contract as MarkItDown's MCP tool.

Input Schema

NameRequiredDescriptionDefault
uriYesThe document to read: an http: or https: URL (only when the server allows URL fetching — see list_input_formats), a file: URI, a data: URI, or a file path. Relative paths resolve against the server's root; files outside it are refused.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.46.0
    • changedInput schema / properties / uri / description
      Previous value: -"The document: an http: or https: URL, a file: URI, a data: URI, or\na path (relative paths resolve against the server's root)."New value: +"The document to read: an http: or https: URL (only when the server\nallows URL fetching — see list_input_formats), a file: URI, a data:\nURI, or a file path. Relative paths resolve against the server's\nroot; files outside it are refused."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds genuine behavioral value by enumerating failure conditions: missing document, path outside the server root, unsupported type, and URL when fetching is disabled. It restates 'Read-only' redundantly but the failure-mode disclosure goes well past the 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?

Front-loads the core purpose and routing decision, then adds format coverage and failure modes. Nearly every sentence earns its place, though the trailing MarkItDown provenance note is extra context that does not help an agent decide or call.

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?

Complete for a default-settings reader with one parameter: it names the return type, the supported formats, the sibling alternatives, and the error conditions. No output schema exists and the description adequately conveys what comes back.

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 coverage is 100% and the single `uri` parameter is fully documented in the schema, including the http/file/data/path forms and relative-path resolution. The description mostly restates that contract rather than adding syntax or format detail, so the baseline 3 applies.

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?

States a specific verb and resource ('Read a document as Markdown ... return the Markdown text') and immediately distinguishes itself from the sibling by naming `convert` as the tool for non-Markdown output. An agent can tell the two apart without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use this whenever Markdown is all you need' and names the alternative tool `convert` plus the exact conditions that select it (other output formats, embedded images, page range, OCR language, password). This is the when-and-when-not pattern at full strength.

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