Skip to main content
Glama
hyunjae-labs

xlwings Excel MCP Server

by hyunjae-labs

delete_worksheet

Remove a specific worksheet from an Excel workbook using the xlwings Excel MCP Server. Specify the workbook session and sheet name to delete unwanted worksheets.

Instructions

Delete worksheet from workbook.

Args:
    session_id: Session ID from open_workbook (required)
    sheet_name: Name of the worksheet to delete

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYes
sheet_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Main tool handler decorated with @mcp.tool(). Validates session, acquires lock, imports and calls the xlwings implementation delete_worksheet_xlw_with_wb, handles errors and returns result message.
    def delete_worksheet(
        session_id: str,
        sheet_name: str
    ) -> str:
        """
        Delete worksheet from workbook.
        
        Args:
            session_id: Session ID from open_workbook (required)
            sheet_name: Name of the worksheet to delete
        """
        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 delete_worksheet_xlw_with_wb
                result = delete_worksheet_xlw_with_wb(session.workbook, sheet_name)
            
            return result.get("message", "Worksheet deleted 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 deleting worksheet: {e}")
            raise
  • Core xlwings implementation for deleting a worksheet using an existing workbook object (session-based). Checks if sheet exists and is not the only one, deletes it via wb.sheets[sheet_name].delete(), saves the workbook, returns success/error dict.
    def delete_worksheet_xlw_with_wb(wb, sheet_name: str) -> Dict[str, Any]:
        """Session-based version using existing workbook object.
        
        Args:
            wb: Workbook object from session
            sheet_name: 삭제할 시트명
            
        Returns:
            삭제 결과 딕셔너리
        """
        try:
            # 시트 존재 확인
            existing_sheets = [sheet.name for sheet in wb.sheets]
            if sheet_name not in existing_sheets:
                return {"error": f"Sheet '{sheet_name}' not found"}
            
            # 시트가 1개만 있으면 삭제 불가
            if len(wb.sheets) == 1:
                return {"error": "Cannot delete the only sheet in workbook"}
            
            # 시트 삭제
            wb.sheets[sheet_name].delete()
            
            # 파일 저장
            wb.save()
            
            return {"message": f"Sheet '{sheet_name}' deleted successfully"}
            
        except Exception as e:
            logger.error(f"xlwings 워크시트 삭제 실패: {e}")
            return {"error": f"Failed to delete worksheet: {str(e)}"}
  • Filepath-based xlwings implementation for deleting worksheet. Opens workbook, performs same checks and deletion as session version, cleans up app and workbook resources.
    def delete_worksheet_xlw(filepath: str, sheet_name: str) -> Dict[str, Any]:
        """xlwings를 사용한 워크시트 삭제
    
        Args:
            filepath: Excel 파일 경로
            sheet_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 sheet_name not in existing_sheets:
                return {"error": f"Sheet '{sheet_name}' not found"}
            
            # 시트가 1개만 있으면 삭제 불가
            if len(wb.sheets) == 1:
                return {"error": "Cannot delete the only sheet in workbook"}
            
            # 시트 삭제
            wb.sheets[sheet_name].delete()
            
            # 파일 저장
            wb.save()
            
            return {"message": f"Sheet '{sheet_name}' deleted successfully"}
            
        except Exception as e:
            logger.error(f"xlwings 워크시트 삭제 실패: {e}")
            return {"error": f"Failed to delete 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}")
  • The @mcp.tool() decorator registers this function as the MCP tool named "delete_worksheet" with input schema derived from function parameters.
    def delete_worksheet(
        session_id: str,
        sheet_name: str
    ) -> str:
        """
        Delete worksheet from workbook.
        
        Args:
            session_id: Session ID from open_workbook (required)
            sheet_name: Name of the worksheet to delete
        """
        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 delete_worksheet_xlw_with_wb
                result = delete_worksheet_xlw_with_wb(session.workbook, sheet_name)
            
            return result.get("message", "Worksheet deleted 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 deleting worksheet: {e}")
            raise

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",
      -  "sheet_name"
      -]New value: +[
      +  "session_id",
      +  "sheet_name"
      +]
  2. First observed

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided. The description states it deletes a worksheet, implying a destructive action, but does not disclose whether the deletion is permanent, if it requires special permissions, or what the return value indicates (e.g., success/failure).

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 concise with two sentences for the main purpose and two bullet points for parameters. The structure is efficient, though the parameter descriptions could be integrated more smoothly.

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 deletion tool with no annotations and a present output schema, the description lacks completeness. It does not explain the output, error handling, or behavior when the worksheet does not exist, leaving the agent with insufficient context.

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?

With 0% schema description coverage, the description adds meaning: it clarifies session_id as obtained from open_workbook and sheet_name as the worksheet name. However, it does not specify formats or constraints (e.g., sheet_name must exist).

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 the action ('Delete worksheet') and the resource ('workbook'), with a specific verb that distinguishes it from sibling tools like copy_worksheet or rename_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 is provided on when to use this tool versus alternatives (e.g., delete_range, clear contents). There is no mention of prerequisites, such as the worksheet being empty or not protected.

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