Docling MCP

Official

Overview Schema Source Related Servers Discussions Admin

Open list in Docling document

open_list_in_docling_document

Opens a new list group in an existing cached document, enabling you to add list items and nested lists before closing the list context.

Instructions

Open a new list group in an existing document in the local document cache.

This tool begins a list context on the document's internal stack. Once a list is open, only add_list_items_to_list_in_docling_document may be called to populate it. Attempting to add a title, section heading, paragraph, or another list before calling close_list_in_docling_document will raise an error. Nested lists are supported: call open_list_in_docling_document again after adding items to start an inner list, then close each list with close_list_in_docling_document in reverse order.

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": {
      "document_key": "<document_key>"
    },
    "name": "open_list_in_docling_document"
  }
}

Input Schema

Name	Required	Description	Default
`document_key`	Yes	The unique identifier of the document in the local cache.

Output Schema

Name	Required	Description	Default
`document_key`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 1, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only say readOnlyHint=false and destructiveHint=false; the description goes well beyond by disclosing stack semantics, the error condition for misordered calls, and the nesting/close-order protocol. This is exactly the kind of state-machine behavior an agent cannot infer from the schema.

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?

Three sentences, front-loaded with the core action, then the constraint, then the nesting rule. No filler and no repetition of the schema 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?

Output schema exists so return values needn't be explained, and the description covers the one thing that matters for this low-parameter tool: the ordering contract and the legal next call. Nothing needed for correct invocation is missing.

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 document_key parameter is fully described in the schema, so the description adds nothing new about it. With one well-documented parameter, the baseline 3 applies rather than a penalty.

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 ('Open a new list group') and scopes it to 'an existing document in the local document cache'. The stateful-stack framing clearly distinguishes it from add_list_items_to_list_in_docling_document and close_list_in_docling_document among the siblings.

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 names the only legal follow-up call (add_list_items_to_list_in_docling_document) and lists the calls that will raise an error instead (title, section heading, paragraph, another list). It also documents the nested-list sequence and the required reverse-order closing, so the agent knows both when to use it and what must come next.

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