SousChef
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| parse_templateA | Parse a Chef ERB template file and convert to Jinja2. Args: path: Path to the ERB template file. Returns: JSON string with extracted variables and Jinja2-converted template. |
| parse_custom_resourceA | Parse a Chef custom resource or LWRP file. Args: path: Path to the custom resource (.rb) file. Returns: JSON string with extracted properties, actions, and metadata. |
| list_directoryC | List the contents of a directory. Args: path: The path to the directory to list. Returns: A list of filenames in the directory, or an error message. |
| read_fileC | Read the contents of a file. Args: path: The path to the file to read. Returns: The contents of the file, or an error message. |
| read_cookbook_metadataC | Parse Chef cookbook metadata.rb file. Args: path: Path to the metadata.rb file. Returns: Formatted string with extracted metadata. |
| parse_recipeB | Parse a Chef recipe file and extract resources. Args: path: Path to the recipe (.rb) file. Returns: Formatted string with extracted Chef resources and their properties. |
| parse_attributesC | Parse a Chef attributes file and extract attribute definitions. Args: path: Path to the attributes (.rb) file. Returns: Formatted string with extracted attributes. |
| list_cookbook_structureC | List the structure of a Chef cookbook directory. Args: path: Path to the cookbook root directory. Returns: Formatted string showing the cookbook structure. |
| convert_resource_to_taskB | Convert a Chef resource to an Ansible task. Args: resource_type: The Chef resource type (e.g., 'package', 'service'). resource_name: The name of the resource. action: The Chef action (e.g., 'install', 'start', 'create'). Defaults to 'create'. properties: Additional resource properties as a string representation. Returns: YAML representation of the equivalent Ansible task. |
| generate_playbook_from_recipeA | Generate a complete Ansible playbook from a Chef recipe. Args: recipe_path: Path to the Chef recipe (.rb) file. Returns: Complete Ansible playbook in YAML format with tasks, handlers, and variables. |
| convert_chef_search_to_inventoryA | Convert a Chef search query to Ansible inventory patterns and groups. Args: search_query: Chef search query (e.g., "role:web AND environment:production"). Returns: JSON string with Ansible inventory patterns and group definitions. |
| generate_dynamic_inventory_scriptA | Generate a Python dynamic inventory script from Chef search queries. Args: search_queries: JSON string containing Chef search queries and group names. Returns: Complete Python script for Ansible dynamic inventory. |
| analyze_chef_search_patternsC | Analyze Chef recipes/cookbooks to extract search patterns for inventory planning. Args: recipe_or_cookbook_path: Path to Chef recipe file or cookbook directory. Returns: JSON string with discovered search patterns and recommended inventory structure. |
| parse_inspec_profileB | Parse an InSpec profile and extract controls. Args: path: Path to InSpec profile directory or control file (.rb). Returns: JSON string with parsed controls, or error message. |
| convert_inspec_to_testC | Convert InSpec controls to Ansible test format. Args: inspec_path: Path to InSpec profile or control file. output_format: Output format ('testinfra' or 'ansible_assert'). Returns: Converted test code or error message. |
| generate_inspec_from_recipeA | Generate InSpec controls from a Chef recipe. Args: recipe_path: Path to Chef recipe file. Returns: InSpec control code or error message. |
| convert_chef_databag_to_varsB | Convert Chef data bag to Ansible variables format. Args: databag_content: JSON content of the Chef data bag databag_name: Name of the data bag item_name: Name of the data bag item (default: "default") is_encrypted: Whether the data bag is encrypted target_scope: Variable scope ("group_vars", "host_vars", or "playbook") Returns: Ansible variables YAML content or vault file structure |
| generate_ansible_vault_from_databagsB | Generate Ansible Vault files from Chef data bags directory. Args: databags_directory: Path to Chef data_bags directory output_directory: Target directory for Ansible variables (group_vars/host_vars) encryption_key_hint: Hint for identifying encrypted data bags Returns: Summary of converted data bags and instructions |
| analyze_chef_databag_usageA | Analyze Chef cookbook for data bag usage and provide migration recommendations. Args: cookbook_path: Path to Chef cookbook databags_path: Optional path to data_bags directory for cross-reference Returns: Analysis of data bag usage and migration recommendations |
| convert_chef_environment_to_inventory_groupA | Convert Chef environment to Ansible inventory group with variables. Args: environment_content: Ruby content of the Chef environment file environment_name: Name of the Chef environment include_constraints: Whether to include cookbook version constraints Returns: Ansible inventory group configuration with variables |
| generate_inventory_from_chef_environmentsB | Generate complete Ansible inventory from Chef environments directory. Args: environments_directory: Path to Chef environments directory output_format: Output format ("yaml", "ini", or "both") Returns: Complete Ansible inventory structure with environment-based groups |
| analyze_chef_environment_usageC | Analyze Chef cookbook for environment usage and provide migration recommendations. Args: cookbook_path: Path to Chef cookbook environments_path: Optional path to environments directory for cross-reference Returns: Analysis of environment usage and migration recommendations |
| generate_awx_job_template_from_cookbookB | Generate AWX/AAP job template configuration from Chef cookbook. Args: cookbook_path: Path to Chef cookbook directory cookbook_name: Name of the cookbook for job template target_environment: Target environment for the job template include_survey: Whether to include survey spec for cookbook attributes Returns: AWX/AAP job template JSON configuration |
| generate_awx_workflow_from_chef_runlistC | Generate AWX/AAP workflow template from Chef runlist. Args: runlist_content: Chef runlist content (JSON or comma-separated) workflow_name: Name for the workflow template environment: Target environment for workflow execution Returns: AWX/AAP workflow template configuration with job dependencies |
| generate_awx_project_from_cookbooksA | Generate AWX/AAP project configuration from Chef cookbooks directory. Args: cookbooks_directory: Path to Chef cookbooks directory project_name: Name for the AWX project scm_type: SCM type (git, svn, etc.) scm_url: SCM repository URL Returns: AWX/AAP project configuration with converted playbooks structure |
| generate_awx_inventory_source_from_chefB | Generate AWX/AAP inventory source from Chef server configuration. Args: chef_server_url: Chef server URL for inventory sync organization: AWX organization name sync_schedule: Inventory sync schedule (hourly, daily, weekly) Returns: AWX/AAP inventory source configuration for Chef server integration |
| convert_chef_deployment_to_ansible_strategyA | Convert Chef application deployment recipe to Ansible deployment strategy. Args: deployment_recipe_path: Path to Chef deployment recipe deployment_pattern: Chef deployment pattern (blue_green, rolling, canary, auto_detect) target_strategy: Target Ansible strategy (rolling_update, blue_green, canary) Returns: Ansible playbook with deployment strategy implementation |
| generate_blue_green_deployment_playbookB | Generate Ansible blue/green deployment playbook from application configuration. Args: app_name: Name of the application to deploy service_config: JSON configuration for service setup health_check_url: URL endpoint for health checks Returns: Complete blue/green deployment playbook with rollback capabilities |
| generate_canary_deployment_strategyC | Generate Ansible canary deployment strategy with gradual rollout. Args: app_name: Name of the application for canary deployment canary_percentage: Initial canary traffic percentage rollout_steps: Comma-separated rollout percentages Returns: Canary deployment strategy with monitoring and automated rollback |
| analyze_chef_application_patternsC | Analyze Chef cookbook for application deployment patterns and provide migration recommendations. Args: cookbook_path: Path to Chef application cookbook application_type: Type of application (web_application, microservice, database, etc.) Returns: Analysis of deployment patterns with Ansible migration recommendations |
| assess_chef_migration_complexityC | Assess the complexity of migrating Chef cookbooks to Ansible with detailed analysis. Args: cookbook_paths: Comma-separated paths to Chef cookbooks or cookbook directory migration_scope: Scope of migration (full, recipes_only, infrastructure_only) target_platform: Target platform (ansible_awx, ansible_core, ansible_tower) Returns: Comprehensive migration complexity assessment with recommendations |
| generate_migration_planA | Generate a detailed migration plan from Chef to Ansible with timeline and milestones. Args: cookbook_paths: Comma-separated paths to Chef cookbooks migration_strategy: Migration approach (big_bang, phased, parallel) timeline_weeks: Target timeline in weeks Returns: Detailed migration plan with phases, milestones, and deliverables |
| analyze_cookbook_dependenciesC | Analyze cookbook dependencies and identify migration order requirements. Args: cookbook_path: Path to Chef cookbook or cookbooks directory dependency_depth: Analysis depth (direct, transitive, full) Returns: Dependency analysis with migration order recommendations |
| generate_migration_reportC | Generate comprehensive migration report from assessment results. Args: assessment_results: JSON string or summary of assessment results report_format: Report format (executive, technical, combined) include_technical_details: Include detailed technical analysis (yes/no) Returns: Formatted migration report for stakeholders |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 34 tools
The tools have clear purposes focused on Chef-to-Ansible migration, but significant overlap exists between analysis tools (e.g., analyze_chef_application_patterns, analyze_chef_databag_usage, analyze_chef_environment_usage) and conversion tools (e.g., convert_chef_databag_to_vars, convert_chef_environment_to_inventory_group). While descriptions help differentiate, an agent might struggle to choose between similar analysis or conversion tools for specific migration tasks, leading to potential misselection.
Most tools follow a consistent verb_noun pattern (e.g., analyze_chef_application_patterns, convert_chef_databag_to_vars, generate_ansible_vault_from_databags), which aids predictability. However, there are minor deviations like list_directory and read_file, which use simpler verbs without the domain prefix, slightly breaking the pattern but remaining readable overall.
With 34 tools, the count is excessive for the Chef-to-Ansible migration domain. Many tools could be consolidated (e.g., multiple analysis and conversion tools overlap in functionality), making the set feel heavy and overwhelming. A more streamlined set of 10-20 tools would better serve the purpose without sacrificing coverage.
The tool set provides comprehensive coverage for Chef-to-Ansible migration, including analysis, conversion, generation of Ansible components (playbooks, inventory, vaults), integration with AWX/AAP, deployment strategies, and reporting. It supports full CRUD/lifecycle operations for the domain, with no obvious gaps that would cause agent failures in migration workflows.