[1Chat] Add support for structured tool call results

[sorenlouv]

Closes https://github.com/elastic/search-team/issues/10552

This PR implements structured tool results (outlined in Content Artifacts RFC). This will form the foundation for citations, visualizations, and query (re-)execution.

Breaking Change: Modified tool handler contract from { result: T } to { results: ToolResult[] }

4 tool result types are defined:

• ResourceResult

• TabularDataResult

• QueryResult

• OtherResult

• Closing https://github.com/elastic/search-team/issues/10553

[joemcelroy]

still need to go through the code changes but found a couple of points whilst testing this:

suggestion: errors should have a "error" structured type rather than using the "other"

{
    "type": "tool_call",
    "tool_call_id": "call_HvVM1uSBbv3jj9hXbwhNW2jT",
    "tool_id": ".execute_esql",
    "params": {
    "query": "FROM financial_accounts | SORT BY total_portfolio_value DESC | LIMIT 1"
    },
    "results": [
        {
            "type": "other",
            "data": {
            "reason": """parsing_exception
    Root causes:
        parsing_exception: line 1:32: extraneous input 'BY' expecting {QUOTED_STRING, INTEGER_LITERAL, DECIMAL_LITERAL, 'false', 'not', 'null', '?', 'true', '+', '-', '??', NAMED_OR_POSITIONAL_PARAM, NAMED_OR_POSITIONAL_DOUBLE_PARAMS, '[', '(', UNQUOTED_IDENTIFIER, QUOTED_IDENTIFIER}"""
            }
        }
    ]
}

question: noticed the index_mapping_response was using the "other" type but seems to have another type below. Is this intentional?

{
    "type": "tool_call",
    "tool_call_id": "call_5w5JIn2trsWEaIeNUrF0XOKJ",
    "tool_id": ".get_index_mapping",
    "params": {
      "indices": [
        "financial_accounts"
      ]
    },
    "results": [
      {
        "type": "other",
        "data": {
          "type": "index_mappings_response",
          "mappings": {
            "financial_accounts": {
              "mappings": {
                "properties": {
                  "account_holder_name": {
                    "type": "text"
                  },
                  "account_id": {
                    "type": "keyword"
                  },
                  "account_type": {
                    "type": "keyword"
                  },
                  "contact_preference": {
                    "type": "keyword"
                  },
                  "first_name": {
                    "type": "text"
                  },
                  "last_name": {
                    "type": "text"
                  },
                  "last_updated": {
                    "type": "date"
                  },
                  "risk_profile": {
                    "type": "keyword"
                  },
                  "state": {
                    "type": "keyword"
                  },
                  "total_portfolio_value": {
                    "type": "double"
                  },
                  "zip_code": {
                    "type": "keyword"
                  }
                }
              }
            }
          },
          "indices": [
            "financial_accounts"
          ]
        }
      }
    ]
  },

[sorenlouv]

question: noticed the index_mapping_response was using the "other" type but seems to have another type below. Is this intentional?

I was toying with the idea of providing a subtype to "other" to distinguish between different "other" artifacts. It's probably a bad idea for now so will remove it.

[joemcelroy]

@elasticmachine merge upstream

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 3b581f4

Metrics [docs]

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
@kbn/onechat-genai-utils	75	74	-1

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
onechat	592.3KB	592.4KB	+38.0B

Public APIs missing exports

Total count of every type that is part of your API that should be exported but is not. This will cause broken links in the API documentation system. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats exports for more detailed information.

id	before	after	diff
@kbn/onechat-common	0	1	+1

Unknown metric groups

API count

id	before	after	diff
@kbn/onechat-genai-utils	79	78	-1

History

• 💚 Build #325440 succeeded 41c531a
• 💚 Build #324873 succeeded 347f896
• 💚 Build #324749 succeeded 1225759
• 💚 Build #324604 succeeded 662239e
• 💚 Build #324418 succeeded 772f184