LibreOffice MCP Tools

document_create

Create new text documents, spreadsheets, or presentations and save them to a specified location using LibreOffice MCP Tools.

Instructions

Create a new empty document and open it. Returns a docId. Supports creating: writer (text document → .docx), calc (spreadsheet → .xlsx), impress (presentation → .pptx).

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": {
      "documentType": "<documentType>",
      "filePath": "<filePath>"
    },
    "name": "document_create"
  }
}

Input Schema

Name	Required	Description	Default
`documentType`	Yes	Type of document to create
`filePath`	Yes	Path where the new document will be saved

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Apr 21, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden. It mentions 'open it' and returns a docId, but doesn't disclose important behavioral traits like whether this requires write permissions, if the file is saved immediately, what happens if filePath exists, or error conditions. The description is insufficient for a mutation tool.

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 sentences with zero waste. First sentence states core functionality and return value. Second sentence efficiently lists supported document types with their file extensions. Perfectly front-loaded and appropriately sized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a creation/mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'open it' means operationally, doesn't mention permissions or side effects, and provides minimal context about the returned docId. Should do more given the tool's complexity.

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%, so the schema already documents both parameters well. The description adds minimal value by listing the three documentType enum values and mentioning filePath, but doesn't provide additional semantics beyond what's in the schema. Baseline 3 is appropriate.

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 clearly states the action ('Create a new empty document and open it') and the resource (document), with specific document types listed. It distinguishes from siblings like document_open (opens existing) or document_convert (converts format).

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?

The description implies usage for creating new documents, but doesn't explicitly state when to use this vs. alternatives like document_open for existing files or document_convert for format changes. It provides context but lacks explicit guidance on exclusions or prerequisites.

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