Office-MCP-Server

Overview Schema Source Related Servers Discussions Admin

word_convert_to_pdf

Convert Word documents (.docx) to PDF using local LibreOffice installation. Specify the file path and optional output path for direct conversion.

Instructions

Convert a .docx file to PDF via a local LibreOffice install (requires LibreOffice/'soffice' on PATH or a standard install location)

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": {
      "file_path": "<file_path>"
    },
    "name": "word_convert_to_pdf"
  }
}

Input Schema

Name	Required	Description	Default
`file_path`	Yes	Absolute path to the .docx file
`output_path`	No	Absolute path to write the PDF to (default: file_path with a .pdf extension)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 5, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the key external dependency on LibreOffice, which is valuable. However, it does not mention error handling, file overwrite behavior, or what happens if the conversion fails, leaving some behavioral gaps.

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 a single, front-loaded sentence with no wasted words. It states the action, the target, and a critical prerequisite in under 25 words — ideal conciseness.

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

Completeness4/5

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

For a simple conversion tool with two well-documented parameters and no output schema, the description covers the essential context: what it does and the required environment. It doesn't detail failure modes, but the simplicity of the operation makes this acceptable.

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% — both parameters ('file_path' and 'output_path') are described in the schema. The description adds no additional parameter-level semantics beyond reinforcing the default output behavior, so 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 uses a specific verb ('Convert') and resource ('.docx file to PDF'), clearly distinguishing it from sibling tools which handle formatting, reading, or editing Word documents. The phrase 'via a local LibreOffice install' adds necessary operational scope.

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

Usage Guidelines4/5

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

It clearly states the prerequisite (LibreOffice/'soffice' on PATH or standard install location), which implies when the tool can be used. It does not explicitly name alternatives or exclusions, but no sibling tool offers PDF conversion, so the context is sufficient.

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

Deploy Server