Skip to main content
Glama
hyunjae-labs

xlwings Excel MCP Server

by hyunjae-labs

rename_worksheet

Change worksheet names in Excel workbooks through the xlwings Excel MCP Server. Provide session ID, current name, and new name to update sheet labels for better organization.

Instructions

Rename worksheet in workbook.

Args:
    session_id: Session ID from open_workbook (required)
    old_name: Current name of the worksheet
    new_name: New name for the worksheet

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYes
old_nameYes
new_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Registration and handler for the 'rename_worksheet' MCP tool. Validates session and delegates to xlwings implementation.
    @mcp.tool()
    def rename_worksheet(
        session_id: str,
        old_name: str,
        new_name: str
    ) -> str:
        """
        Rename worksheet in workbook.
        
        Args:
            session_id: Session ID from open_workbook (required)
            old_name: Current name of the worksheet
            new_name: New name for the worksheet
        """
        try:
            # Validate session using centralized helper
            session = get_validated_session(session_id)
            if isinstance(session, str):  # Error message returned
                return session
                
            with session.lock:
                from xlwings_mcp.xlwings_impl.sheet_xlw import rename_worksheet_xlw_with_wb
                result = rename_worksheet_xlw_with_wb(session.workbook, old_name, new_name)
            
            return result.get("message", "Worksheet renamed successfully") if "error" not in result else f"Error: {result['error']}"
            
        except (ValidationError, SheetError) as e:
            return f"Error: {str(e)}"
        except Exception as e:
            logger.error(f"Error renaming worksheet: {e}")
            raise
  • Core xlwings implementation for renaming a worksheet using an existing workbook object (session-based). Performs validation, renames sheet, and saves.
    def rename_worksheet_xlw_with_wb(wb, old_name: str, new_name: str) -> Dict[str, Any]:
        """Session-based version using existing workbook object.
        
        Args:
            wb: Workbook object from session
            old_name: 기존 시트명
            new_name: 새 시트명
            
        Returns:
            이름 변경 결과 딕셔너리
        """
        try:
            # 기존 시트 확인
            existing_sheets = [sheet.name for sheet in wb.sheets]
            if old_name not in existing_sheets:
                return {"error": f"Sheet '{old_name}' not found"}
            
            # 새 이름 중복 확인
            if new_name in existing_sheets:
                return {"error": f"Sheet '{new_name}' already exists"}
            
            # 시트 이름 변경
            wb.sheets[old_name].name = new_name
            
            # 파일 저장
            wb.save()
            
            return {"message": f"Sheet renamed from '{old_name}' to '{new_name}'"}
            
        except Exception as e:
            logger.error(f"xlwings 워크시트 이름 변경 실패: {e}")
            return {"error": f"Failed to rename worksheet: {str(e)}"}
  • Wrapper function in sheet.py that calls the non-session xlwings rename_worksheet_xlw implementation (legacy/non-primary path).
    def rename_sheet(filepath: str, old_name: str, new_name: str) -> Dict[str, Any]:
        """Rename a worksheet."""
        result = rename_worksheet_xlw(filepath, old_name, new_name)
        if "error" in result:
            raise SheetError(result["error"])
        return result
  • Non-session (filepath-based) xlwings implementation for renaming worksheet. Opens workbook, renames, saves, and cleans up Excel app.
    def rename_worksheet_xlw(filepath: str, old_name: str, new_name: str) -> Dict[str, Any]:
        """xlwings를 사용한 워크시트 이름 변경
    
        Args:
            filepath: Excel 파일 경로
            old_name: 기존 시트명
            new_name: 새 시트명
    
        Returns:
            이름 변경 결과 딕셔너리
        """
        app = None
        wb = None
    
        # Initialize COM for thread safety (Windows)
        _com_initialize()
    
        try:
            # 파일 경로 검증
            file_path = Path(filepath)
            if not file_path.exists():
                return {"error": f"File not found: {filepath}"}
            
            # Excel 앱 시작
            app = xw.App(visible=False, add_book=False)
            
            # 워크북 열기
            wb = app.books.open(filepath)
            
            # 기존 시트 확인
            existing_sheets = [sheet.name for sheet in wb.sheets]
            if old_name not in existing_sheets:
                return {"error": f"Sheet '{old_name}' not found"}
            
            # 새 이름 중복 확인
            if new_name in existing_sheets:
                return {"error": f"Sheet '{new_name}' already exists"}
            
            # 시트 이름 변경
            wb.sheets[old_name].name = new_name
            
            # 파일 저장
            wb.save()
            
            return {"message": f"Sheet renamed from '{old_name}' to '{new_name}'"}
            
        except Exception as e:
            logger.error(f"xlwings 워크시트 이름 변경 실패: {e}")
            return {"error": f"Failed to rename worksheet: {str(e)}"}
            
        finally:
            # 리소스 정리
            if wb:
                try:
                    wb.close()
                except Exception as e:
                    logger.warning(f"워크북 닫기 실패: {e}")
            
            if app:
                try:
                    app.quit()
                except Exception as e:
                    logger.warning(f"Excel 앱 종료 실패: {e}")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / filepath
      Removed value: -{
      -  "title": "Filepath",
      -  "type": "string"
      -}
    • addedInput schema / properties / session_id
      Added value: +{
      +  "title": "Session Id",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "filepath",
      -  "old_name",
      -  "new_name"
      -]New value: +[
      +  "session_id",
      +  "old_name",
      +  "new_name"
      +]
  2. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as whether the rename is reversible, if it triggers any side effects, or if specific permissions are needed. It simply states the action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and to the point, but includes an Args section that is somewhat verbose for a tool description. Could be more concise by integrating parameter details inline.

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

Completeness3/5

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

Given the presence of an output schema (not detailed here), the description adequately covers the basics but lacks usage context and differentiation from similar tools. It is minimally complete for a simple rename operation.

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 0%, but the description adds minimal meaning by explaining session_id as 'from open_workbook (required)' and naming the other parameters. However, it lacks details like valid name formats or constraints.

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 'Rename worksheet in workbook', which is a specific verb and resource. It distinguishes itself from sibling tools like copy_worksheet or delete_worksheet.

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, or any prerequisites beyond the session_id being from open_workbook. Does not mention that the worksheet must exist or that old_name must match exactly.

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