We had considered exposing all ECA action plugins to AI, especially to agents and to MCP, but it turns out that for 2 reasons that's not a valid approach:
Instead, let's expose custom events. They are the starting point for small or large models that provide some functionality, taking specified input and provide their result as structured output.
Let's enhance the custom event configuration such that the user can optionally provide extra metadata like input specification, description, etc., and then provide a plugin deriver to expose that custom event as a plugin implementing \Drupal\ai\Service\FunctionCalling\ExecutableFunctionCallInterface.
Active
3.0
Code
Instead of "mis-using" the custom event, let's introduce a tools event for this.
Here is a test model with 2 tools that can be tested with the Tools Explorer from the AI module.