You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current tool implementation has quite a few drawbacks and we can enhance this by supporting dynamic tools in agent framework, the implementation of it needs a little change in /agents/_register and /agents/execute API, more details can be found in this issue: opensearch-project/skills#459
The text was updated successfully, but these errors were encountered:
Sure, there are limited changes in ml-commons.
In agents/_register API:
MLToolSpec needs to add a new field private List<MLToolSpec> toolSpecList to support the new dynamical tool definition.
In agents/_execute API:
The toolSpectList needs to be passed into the parameters map(tool interface run method arg) when running the tool.
I also have the plan to change ml-commons project structure and tool's interface to extract the MLToolSpec to a separate module so that it can be depended by ml-algorithms and spi modules to mitigate the seder effort between agent running and tool running, e.g. an object parameter might need to serialized to string to put it into Map<String, String> parameters and then deserialize it back to an object in tool's run method. This needs much more effort in both ml-commons and skills so this is a future plan.
The current tool implementation has quite a few drawbacks and we can enhance this by supporting dynamic tools in agent framework, the implementation of it needs a little change in
/agents/_register
and/agents/execute
API, more details can be found in this issue: opensearch-project/skills#459The text was updated successfully, but these errors were encountered: