Leveraging declarative tools definitions (YAML files)

[dtehan-td]

veraging declarative tools definitions (YAML files) and server customization. So that tools can be easily modified in the field we want tools defined using the declarative approach where we define the tool in yaml. We have a number of tools that have been developed to configure an environment, we would like to explore an alternative approach to configurations.

1. Determine an approach within to address configuration requirements that works with the declarative framework
2. Move as many tools as possible from Python code to YAML for better maintainability.
3. Identify tool modules that can be moved to Skills/prompts and custom tool definitions (provided under the server configuration examples as opposed to packaged within the source code), the target is every module except the explicit tool set.

• BAR move to skills and custom tool, need to think about the non-standard configuration steps
• Base - some to become explicit, rest will go to custom tool
• Chat module - move to custom tool, need to think about the non-standard configuration steps
• DBA - move all to custom tool
• FS - move to skills/prompts and custom tool
• Plot - move to skills/prompts and custom tool
• Qlty - move to custom tool
• Rag - move to skills/prompts and custom tool
• Sec - move to custom tool
• Sql_opt - move to skill/prompts and custom tool
• TDVS - are these required given the skills from the cookbooks
• TDML Tools - are these required given the skills from the cookbooks