Skip to main content
Glama
GongRzhe

Office Word MCP Server

protect_document

Add password protection to Microsoft Word documents to restrict unauthorized access and secure sensitive information.

Instructions

Add password protection to a Word document.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameYes
passwordYes

Implementation Reference

  • Core handler function implementing password protection logic using msoffcrypto to encrypt the Word document.
    async def protect_document(filename: str, password: str) -> str:
        """Add password protection to a Word document.
    
        Args:
            filename: Path to the Word document
            password: Password to protect the document with
        """
        filename = ensure_docx_extension(filename)
    
        if not os.path.exists(filename):
            return f"Document {filename} does not exist"
    
        # Check if file is writeable
        is_writeable, error_message = check_file_writeable(filename)
        if not is_writeable:
            return f"Cannot protect document: {error_message}"
    
        try:
            # Read the original file content
            with open(filename, "rb") as infile:
                original_data = infile.read()
    
            # Create an msoffcrypto file object from the original data
            file = msoffcrypto.OfficeFile(io.BytesIO(original_data))
            file.load_key(password=password) # Set the password for encryption
    
            # Encrypt the data into an in-memory buffer
            encrypted_data_io = io.BytesIO()
            
            file.encrypt(password=password, outfile=encrypted_data_io) 
    
            # Overwrite the original file with the encrypted data
            with open(filename, "wb") as outfile:
                outfile.write(encrypted_data_io.getvalue())
    
            
            base_path, _ = os.path.splitext(filename)
            metadata_path = f"{base_path}.protection"
            if os.path.exists(metadata_path):
                os.remove(metadata_path)
    
            return f"Document {filename} encrypted successfully with password."
    
        except Exception as e:
            # Attempt to restore original file content on failure
            try:
                if 'original_data' in locals():
                    with open(filename, "wb") as outfile:
                        outfile.write(original_data)
                    return f"Failed to encrypt document {filename}: {str(e)}. Original file restored."
                else:
                     return f"Failed to encrypt document {filename}: {str(e)}. Could not restore original file."
            except Exception as restore_e:
                 return f"Failed to encrypt document {filename}: {str(e)}. Also failed to restore original file: {str(restore_e)}"
  • MCP tool registration using FastMCP @mcp.tool() decorator. Thin wrapper delegating to protection_tools.protect_document.
    @mcp.tool()
    def protect_document(filename: str, password: str):
        """Add password protection to a Word document."""
        return protection_tools.protect_document(filename, password)
  • Export of protect_document function from protection_tools module for use in main.py.
    from word_document_server.tools.protection_tools import (
        protect_document, add_restricted_editing,
        add_digital_signature, verify_document
    )
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool adds password protection but doesn't mention important behavioral aspects: whether this is a destructive/mutative operation, what permissions are required, how the password is stored/encrypted, whether the original document is modified or a new one created, or what happens on failure.

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 appropriately sized for a simple tool and front-loads the core functionality immediately.

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 mutation tool with no annotations, no output schema, and 0% schema description coverage, the description is inadequate. It doesn't explain what happens after protection is added, what the return value is, error conditions, or important behavioral constraints. The context signals indicate significant gaps in documentation.

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 undocumented parameters. It mentions 'Word document' which hints at the 'filename' parameter, and 'password protection' hints at the 'password' parameter, but provides no details about filename format/path, password requirements/strength, or other constraints. This adds minimal value beyond what's obvious from 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 action ('Add password protection') and resource ('to a Word document'), providing specific verb+resource. However, it doesn't differentiate from sibling tools like 'unprotect_document' or explain how it differs from other document modification tools.

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?

No guidance on when to use this tool versus alternatives is provided. The description doesn't mention prerequisites (e.g., document must exist), when not to use it, or how it relates to sibling tools like 'unprotect_document' or other document security tools.

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