Cross-document tool response mechanism #135
Description
Should the agent receive a response from the next page, after a declarative <form> tool navigates? This is mostly a follow-up to #76 (comment) and #76 (comment), where the whole concept of using the form target page's <script type=application/ld+json> contents as the tool's response, and possible using the entire HTML page as a back-up if the JSON-LD doesn't exist.
This whole mechanism came about after discussion about how agents ingest structured data like markdown and JSON better than HTML, and when an agent actuates a declarative tool that triggers a navigation. We considered introducing a new script type in the target page that contained structured data representing the target page's contents, but then realized that many of the target pages would have this already in the form of JSON-LD, so we considered re-using this.
But some good alternatives that were discussed are:
- A
<context>,<resource>, or other kind of purpose-built element to shuttle target-page data to the tool that triggered the navigation - A simple, standardized "the navigation succeeded" message, with no information specific to the target page
- Unconditionally the full HTML response to the agent as the tool's "response"
I will note that this relates to #9, since the task of defining an output schema for a form tool is tricky, so connecting the form to the shape of data on the other side of the navigation is something to consider.