Problem/Motivation

Tool module is the next generation of actions, with TypedData integration, PHP attributes, etc, and enables many features including easier agentic integration. See e.g. https://dri.es/one-description-inside-and-outside-drupal about its potential.

Steps to reproduce

n.a.

Proposed resolution

Module support is implemented, or a decision is justified to not implement it.

Remaining tasks

  • Identify actual potential uses. Given how much domain logic G2 contains about what makes up a glossary, there should be multiple capabilities. If that fails, document why we won't be adding that.
  • If step one doesn't fail, start work in the next major branch, as it will likely rely on a different storage model, and possibly different APIs
  • Create a series of followup issues, starting with the base integration and adding issues per feature
  • Check what in the current implementation can be replaced by tool use for a leaner code base, issues per cleanup
  • Add that in an actual release

User interface changes

Some UI redesign might become possible, none is decided yet.

API changes

  • Expose the tool API
  • TBD: This will probably enable disabling legacy APIs like XML-RPC once they have a replacement

Data model changes

TBD

Comments

fgm created an issue.