Skip to main content
Glama
GongRzhe

Office Word MCP Server

set_table_column_widths

Adjust table column widths in Word documents to improve layout and readability by specifying exact measurements for multiple columns at once.

Instructions

Set the widths of multiple table columns.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameYes
table_indexYes
widthsYes
width_typeNopoints

Implementation Reference

  • The primary asynchronous handler implementing the tool logic: input validation, document loading, width unit conversion, calling low-level helper, saving the document, and error handling.
    async def set_table_column_widths(filename: str, table_index: int, widths: list, 
                                     width_type: str = "points") -> str:
        """Set the widths of multiple table columns.
        
        Args:
            filename: Path to the Word document
            table_index: Index of the table (0-based)
            widths: List of width values for each column
            width_type: Width type ("points", "inches", "cm", "percent", "auto")
        """
        filename = ensure_docx_extension(filename)
        
        # Ensure numeric parameters are the correct type
        try:
            table_index = int(table_index)
            if width_type != "auto":
                widths = [float(w) for w in widths]
        except (ValueError, TypeError):
            return "Invalid parameter: table_index must be an integer, widths must be a list of numbers"
        
        # Validate width type
        valid_width_types = ["points", "inches", "cm", "percent", "auto"]
        if width_type.lower() not in valid_width_types:
            return f"Invalid width type. Valid options: {', '.join(valid_width_types)}"
        
        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 modify document: {error_message}. Consider creating a copy first."
        
        try:
            doc = Document(filename)
            
            # Validate table index
            if table_index < 0 or table_index >= len(doc.tables):
                return f"Invalid table index. Document has {len(doc.tables)} tables (0-{len(doc.tables)-1})."
            
            table = doc.tables[table_index]
            
            # Convert widths and type for Word format
            word_widths = []
            for width in widths:
                if width_type.lower() == "points":
                    word_widths.append(width)
                elif width_type.lower() == "inches":
                    word_widths.append(width * 72)  # 72 points per inch
                elif width_type.lower() == "cm":
                    word_widths.append(width * 28.35)  # ~28.35 points per cm
                elif width_type.lower() == "percent":
                    word_widths.append(width)
                else:  # auto
                    word_widths.append(0)
            
            # Determine Word type
            if width_type.lower() == "percent":
                word_type = "pct"
            elif width_type.lower() == "auto":
                word_type = "auto"
            else:
                word_type = "dxa"
            
            # Apply column widths
            success = set_column_widths(table, word_widths, word_type)
            
            if success:
                doc.save(filename)
                return f"Column widths set successfully for table {table_index} with {len(widths)} columns in {width_type}."
            else:
                return f"Failed to set column widths."
        except Exception as e:
            return f"Failed to set column widths: {str(e)}"
  • MCP tool registration using @mcp.tool() decorator on a synchronous wrapper function that delegates to the async implementation in format_tools.
    @mcp.tool()
    def set_table_column_widths(filename: str, table_index: int, widths: list, 
                               width_type: str = "points"):
        """Set the widths of multiple table columns."""
        return format_tools.set_table_column_widths(filename, table_index, widths, width_type)
  • Low-level helper utility that iterates over columns and sets individual column widths using XML elements, handling multiple columns.
    def set_column_widths(table, widths, width_type="dxa"):
        """
        Set widths for multiple columns in a table.
        
        Args:
            table: The table to modify
            widths: List of width values for each column
            width_type: Width type ("dxa" for points*20, "pct" for percentage*50, "auto")
            
        Returns:
            True if successful, False otherwise
        """
        try:
            for col_index, width in enumerate(widths):
                if col_index >= len(table.columns):
                    break
                if not set_column_width(table, col_index, width, width_type):
                    return False
            return True
        except Exception as e:
            print(f"Error setting column widths: {e}")
            return False
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies a mutation ('Set'), but doesn't disclose whether this operation is destructive, requires specific permissions, or has side effects (e.g., affecting document layout). No information about error conditions, validation of widths, or response format is included.

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 that front-loads the core purpose without unnecessary words. Every word earns its place, making it easy to parse quickly despite its brevity.

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 4 parameters (3 required), 0% schema coverage, and no output schema, the description is inadequate. It lacks essential context about parameter meanings, behavioral expectations, error handling, and relationship to sibling tools, leaving significant gaps for an AI agent to infer.

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 but fails to do so. It mentions 'multiple table columns' which hints at the 'widths' array parameter, but doesn't explain 'filename', 'table_index', or 'width_type' (despite its default value). No details about width units, array format, or table indexing are provided.

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 ('Set') and target resource ('widths of multiple table columns'), making the purpose immediately understandable. It distinguishes itself from sibling 'set_table_column_width' (singular) by specifying 'multiple' columns, though it doesn't fully differentiate from other table formatting tools like 'format_table' or 'auto_fit_table_columns'.

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 is provided on when to use this tool versus alternatives like 'set_table_column_width' (singular), 'auto_fit_table_columns', or 'format_table'. The description lacks context about prerequisites (e.g., document must exist, table must be present) or typical scenarios for applying column width adjustments.

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