Package com.oracle.database.selectai.model.agent


package com.oracle.database.selectai.model.agent
Configuration, request, response, status, and discovery models for Oracle Select AI Agent operations.

The models in this package are used with the public agent interfaces and represent data exchanged with the DBMS_CLOUD_AI_AGENT PL/SQL package. Builders prepare values locally; constructing a model does not execute a database operation. Built models retain immutable snapshots of their configured collections and maps; builders are mutable and should not be shared across threads without synchronization.

Resource and tool configuration

AgentAttributes, TaskAttributes, ToolAttributes, and TeamAttributes describe creation settings, attribute updates, and attributes loaded from database metadata. AgentStatus, TaskStatus, ToolStatus, and TeamStatus describe resource enablement, not workflow execution state.

ToolParams provides immutable built-in tool configuration through SqlToolParams, RagToolParams, WebSearchToolParams, SlackNotificationToolParams, and EmailNotificationToolParams. GenericToolParams preserves parameters for other database-defined tool types or schemas that cannot be represented by the known models. Known tool-parameter models also retain additional database fields. ToolType is an extensible value object that preserves tool-type values introduced by newer database releases. ToolInput models input names and descriptions in the immutable tool_inputs list exposed by ToolAttributes. Descriptions guide the model and do not enforce supported input values in Java.

Team requests and results

Not every database response has a dedicated model: tool descriptions and exported definitions remain JSON strings. Exported definitions may have an object or array as their top-level JSON value.

Validation

Resource-attribute builders do not require fields that the database validates when a resource is created. They retain documented Java checks, such as numeric ranges and collection structure. Request models validate required arguments and mutually exclusive input forms where documented. The database applies semantic validation and version-specific behavior when operations are executed. See each model's contract for omitted values and validation rules; typed requests do not imply unrestricted raw-JSON support.
Since:
1.1.0
See Also: