✨ feat: enhance tool filtering and specification handling

[pelikhan]

Introduce filtering of tools based on specifications, add intent support.

---

Summary of Changes

This pull request introduces several enhancements and features related to tool management, intent validation, and security for GenAIScript. Here's an overview of the changes:

• ✨ Output Intent Validation for Tools:

  • Added support for validating tool outputs using an "LLM-as-a-Judge" approach to ensure results align with the tool's intent.
  • Introduced the intent property for tools and MCP servers, which can use the tool description or a custom function for validation.
  • Integrated intent validation into the tool execution pipeline, leveraging a lightweight model (small by default) for validation.

• 🔒 Enhanced Security Features:

  • Added detectPromptInjection and intent options to MCP server configurations to strengthen protection against prompt injection and ensure tool output integrity.
  • Updated the toolsSha property to support partial SHA for better readability.

• 🛠️ Improved Tool Specification:

  • Introduced the ability to filter and specify subsets of tools from MCP servers using tools in server configurations.
  • Enhanced tool definitions to include generator context for more robust execution and validation.

• 📊 Visual Enhancements:

  • Added mermaid diagrams to documentation for better visualization of security processes like signature checks and prompt injection detection.

• 📚 Documentation Updates:

  • Updated and expanded documentation for tools, MCP servers, and security features.
  • Added examples for intent validation and tool configurations to guide users.

• 🧪 Sample Scripts:

  • Added new sample scripts (mcp-tools-intent.genai.mts and tool_with_intent.genai.mts) showcasing the use of intent validation and custom tool configurations.

• 🐛 Miscellaneous Improvements:

  • Refactored debug logging for better readability and traceability.
  • Renamed functions to tools in prompt rendering and related code for consistency.

These changes enhance the robustness, security, and usability of GenAIScript, particularly in tool management and validation workflows. 🚀

AI-generated content by prd may be incorrect

---

🚀 Here’s a high-level summary of the changes from the git diff:

• 🔧 Added toMcpToolSpecification function: Accepts either a string (tool name) or an existing specification and returns the same type. This is used to facilitate tool creation in McpClientManager.

• 🎯 Updated tool handling:

  • Added tools filtering: The system now allows filtering tools based on their specified intent, which helps narrow down results during validation.
  • Enhanced McpServerConfig public API: This change ensures better separation of concerns between server configuration and client implementation in prompt templates.

• New interface fields were introduced to standardize type checking in prompt_template.d.ts:

  • Intent field added to DefToolOptions for tool validation purposes.
  • ID field enhanced in McpServerConfig, with an optional tools filter array that points to specific tool configurations by name.

These changes solidify the public API alignment and improve type consistency throughout the codebase.

AI-generated content by pr-describe may be incorrect