Docling MCP

Official

Overview Schema Source Related Servers Discussions Admin

Create new Docling document

create_new_docling_document

Create a new, empty Docling document ready for incremental authoring, then populate it with titles, headings, paragraphs, and lists using related tools.

Instructions

Create a new, empty Docling document ready for incremental authoring.

Use this tool when you want to build a document from scratch by subsequently calling add_title_to_docling_document, add_section_heading_to_docling_document, add_paragraph_to_docling_document, open_list_in_docling_document, and related tools. To convert an already-existing file (PDF, DOCX, HTML, etc.) instead, use convert_document_into_docling_document.

The document is stored in the local cache under a unique key and the prompt text is recorded as a furniture item for reference.

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": {
      "prompt": "<prompt>"
    },
    "name": "create_new_docling_document"
  }
}

Input Schema

Name	Required	Description	Default
`prompt`	Yes	The prompt text to include in the new document.

Output Schema

Name	Required	Description	Default
`prompt`	Yes
`document_key`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 1, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive operation. The description adds useful behavioral context: the document is stored in the local cache under a unique key and the prompt is recorded as a furniture item. It does not cover permission or persistence details, but those are less central here.

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?

The description is compact and front-loaded: primary purpose first, then usage guidance, then the sibling alternative, then storage behavior. Every sentence contributes useful information.

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 simple one-parameter schema, existing output schema, and annotations, the description provides everything needed: creation semantics, incremental authoring context, alternative tool routing, and local cache behavior.

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 single prompt parameter is already documented. The description adds meaning by explaining that the prompt text becomes a furniture item for reference, going beyond the schema's plain input description.

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 states a specific verb and resource: create a new, empty Docling document. It also distinguishes this from the sibling conversion tool and names the downstream authoring tools it is meant to precede.

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?

It gives explicit when-to-use guidance for incremental authoring from scratch and names the alternative convert_document_into_docling_document for existing files. This directly routes the agent between sibling tools.

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