>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3524351. --> Reported by: [marcus_johansson](https://www.drupal.org/user/385947) Related to !126 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Currently the default information tools are added into the system message, which was the initial part of the functionality, but we have found another use case where another way of doing it would be useful.</p> <p>So the initial idea was that for instance something like the Field Agent would need to know what field types exists, that would be some information that needs to be retained through the whole process as pure dynamic information knowledge.</p> <p>However, since we have tokens in the agent, you might actually want to trigger an actual tool that does changes and retain that has memory of a tool that has been run. This means that it will be kept in the chat history of the agent.</p> <p>We already have available_on_loop, that says to inject into system message on one specific instance, but instead we could reutilize this to be used to inject into memory.</p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p><del>Change so when available_on_loop is set, the tool is run, a faked tool_id is set and this is added into the chat history on that loop.</del>Since we will be needing a normalization for how to fake tool_id, we will just set it as a user message for now.</p>