Skip to main content
Glama
GongRzhe

Office Word MCP Server

convert_to_pdf

Convert Word documents to PDF format using the Office Word MCP Server. This tool transforms DOCX files into PDFs for sharing, printing, or archiving.

Instructions

Convert a Word document to PDF format.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameYes
output_filenameNo

Implementation Reference

  • Core asynchronous handler implementing PDF conversion logic for Word documents, supporting Windows (docx2pdf with MS Word), Linux/macOS (LibreOffice headless), with comprehensive error handling and platform detection.
    async def convert_to_pdf(filename: str, output_filename: Optional[str] = None) -> str:
        """Convert a Word document to PDF format.
        
        Args:
            filename: Path to the Word document
            output_filename: Optional path for the output PDF. If not provided, 
                             will use the same name with .pdf extension
        """
        filename = ensure_docx_extension(filename)
        
        if not os.path.exists(filename):
            return f"Document {filename} does not exist"
        
        # Generate output filename if not provided
        if not output_filename:
            base_name, _ = os.path.splitext(filename)
            output_filename = f"{base_name}.pdf"
        elif not output_filename.lower().endswith('.pdf'):
            output_filename = f"{output_filename}.pdf"
        
        # Convert to absolute path if not already
        if not os.path.isabs(output_filename):
            output_filename = os.path.abspath(output_filename)
        
        # Ensure the output directory exists
        output_dir = os.path.dirname(output_filename)
        if not output_dir:
            output_dir = os.path.abspath('.')
        
        # Create the directory if it doesn't exist
        os.makedirs(output_dir, exist_ok=True)
        
        # Check if output file can be written
        is_writeable, error_message = check_file_writeable(output_filename)
        if not is_writeable:
            return f"Cannot create PDF: {error_message} (Path: {output_filename}, Dir: {output_dir})"
        
        try:
            # Determine platform for appropriate conversion method
            system = platform.system()
            
            if system == "Windows":
                # On Windows, try docx2pdf which uses Microsoft Word
                try:
                    from docx2pdf import convert
                    convert(filename, output_filename)
                    return f"Document successfully converted to PDF: {output_filename}"
                except (ImportError, Exception) as e:
                    return f"Failed to convert document to PDF: {str(e)}\nNote: docx2pdf requires Microsoft Word to be installed."
                    
            elif system in ["Linux", "Darwin"]:  # Linux or macOS
                errors = []
                
                # --- Attempt 1: LibreOffice ---
                lo_commands = []
                if system == "Darwin":  # macOS
                    lo_commands = ["soffice", "/Applications/LibreOffice.app/Contents/MacOS/soffice"]
                else:  # Linux
                    lo_commands = ["libreoffice", "soffice"]
    
                for cmd_name in lo_commands:
                    try:
                        output_dir_for_lo = os.path.dirname(output_filename) or '.'
                        os.makedirs(output_dir_for_lo, exist_ok=True)
                        
                        cmd = [cmd_name, '--headless', '--convert-to', 'pdf', '--outdir', output_dir_for_lo, filename]
                        result = subprocess.run(cmd, capture_output=True, text=True, timeout=60, check=False)
    
                        if result.returncode == 0:
                            # LibreOffice typically creates a PDF with the same base name as the source file.
                            # e.g., 'mydoc.docx' -> 'mydoc.pdf'
                            base_name = os.path.splitext(os.path.basename(filename))[0]
                            created_pdf_name = f"{base_name}.pdf"
                            created_pdf_path = os.path.join(output_dir_for_lo, created_pdf_name)
    
                            # If the created file exists, move it to the desired output_filename if necessary.
                            if os.path.exists(created_pdf_path):
                                if created_pdf_path != output_filename:
                                    shutil.move(created_pdf_path, output_filename)
                                
                                # Final check: does the target file now exist?
                                if os.path.exists(output_filename):
                                    return f"Document successfully converted to PDF via {cmd_name}: {output_filename}"
                            
                            # If we get here, soffice returned 0 but the expected file wasn't created.
                            errors.append(f"{cmd_name} returned success code, but output file '{created_pdf_path}' was not found.")
                            # Continue to the next command or fallback.
                        else:
                            errors.append(f"{cmd_name} failed. Stderr: {result.stderr.strip()}")
                    except FileNotFoundError:
                        errors.append(f"Command '{cmd_name}' not found.")
                    except (subprocess.SubprocessError, Exception) as e:
                        errors.append(f"An error occurred with {cmd_name}: {str(e)}")
                
                # --- Attempt 2: docx2pdf (Fallback) ---
                try:
                    from docx2pdf import convert
                    convert(filename, output_filename)
                    if os.path.exists(output_filename) and os.path.getsize(output_filename) > 0:
                        return f"Document successfully converted to PDF via docx2pdf: {output_filename}"
                    else:
                        errors.append("docx2pdf fallback was executed but failed to create a valid output file.")
                except ImportError:
                    errors.append("docx2pdf is not installed, skipping fallback.")
                except Exception as e:
                    errors.append(f"docx2pdf fallback failed with an exception: {str(e)}")
    
                # --- If all attempts failed ---
                error_summary = "Failed to convert document to PDF using all available methods.\n"
                error_summary += "Recorded errors: " + "; ".join(errors) + "\n"
                error_summary += "To convert documents to PDF, please install either:\n"
                error_summary += "1. LibreOffice (recommended for Linux/macOS)\n"
                error_summary += "2. Microsoft Word (required for docx2pdf on Windows/macOS)"
                return error_summary
            else:
                return f"PDF conversion not supported on {system} platform"
                
        except Exception as e:
            return f"Failed to convert document to PDF: {str(e)}"
  • MCP tool registration using FastMCP @mcp.tool() decorator. This synchronous wrapper delegates execution to the async handler in extended_document_tools.
    def convert_to_pdf(filename: str, output_filename: str = None):
        """Convert a Word document to PDF format."""
        return extended_document_tools.convert_to_pdf(filename, output_filename)
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the conversion action but lacks critical details: whether this modifies the original file, where files are located (local paths, cloud storage), authentication needs, error handling for invalid inputs, or output behavior (e.g., where the PDF is saved). 'Convert' implies a write operation, but specifics are missing.

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, efficient sentence with zero wasted words. It's front-loaded with the core action and resource, making it immediately understandable. Every word earns its place by specifying the conversion task and target format.

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 tool with 2 parameters, 0% schema coverage, no annotations, and no output schema, the description is incomplete. It doesn't address parameter meanings, behavioral details (like file handling or errors), or output expectations. While concise, it lacks the necessary context for safe and effective use by an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for two undocumented parameters. It mentions 'Word document' which hints at the 'filename' parameter, but doesn't explain what 'filename' represents (path, URI, etc.) or the optional 'output_filename' parameter at all. The description adds minimal semantic value beyond the tool name.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('Convert') and resource ('Word document to PDF format'). It distinguishes from most sibling tools which focus on document editing, formatting, or information retrieval rather than format conversion. However, it doesn't explicitly differentiate from potential format conversion siblings that might exist in other contexts.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing Word document), exclusions (e.g., what file types are supported beyond 'Word document'), or alternative tools for similar tasks. The sibling list shows no direct PDF-related alternatives, but the description offers no context for decision-making.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GongRzhe/Office-Word-MCP-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server