This repository was archived by the owner on Jul 22, 2025. It is now read-only.
DEV: use a proper object for tool definition #1337
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit introduces a comprehensive refactoring of the AI tools system by adding a proper object-oriented interface for tool definitions. Instead of working with raw hash structures, tools are now represented by a proper
ToolDefinitionclass with validation, parameter coercion, and schema generation capabilities.Key changes:
Add new
ToolDefinitionclass with nestedParameterDefinitionclassparameters_json_schemamethodRefactor all dialect adapters to use the new class:
Improve the
XmlToolProcessorto use tool definitions for parameter coercionChange Ollama environment check to enable in both development and test
Update tests to work with the new object-oriented interface
This change significantly improves code maintainability, type safety, and error handling while reducing duplicated parameter handling code across different LLM integrations.