pub struct CreateQueryToolDto {
pub messages: Option<Vec<CreateDtmfToolDtoMessagesInner>>,
pub type: TypeTrue,
pub knowledge_bases: Option<Vec<KnowledgeBase>>,
pub function: Option<OpenAiFunction>,
}
Fields§
§messages: Option<Vec<CreateDtmfToolDtoMessagesInner>>
These are the messages that will be spoken to the user as the tool is running. For some tools, this is auto-filled based on special fields like tool.destinations
. For others like the function tool, these can be custom configured.
type: TypeTrue
The type of tool. "query" for Query tool.
knowledge_bases: Option<Vec<KnowledgeBase>>
The knowledge bases to query
function: Option<OpenAiFunction>
This is the function definition of the tool. For endCall
, transferCall
, and dtmf
tools, this is auto-filled based on tool-specific fields like tool.destinations
. But, even in those cases, you can provide a custom function definition for advanced use cases. An example of an advanced use case is if you want to customize the message that’s spoken for endCall
tool. You can specify a function where it returns an argument "reason". Then, in messages
array, you can have many "request-complete" messages. One of these messages will be triggered if the messages[].conditions
matches the "reason" argument.
Implementations§
Source§impl CreateQueryToolDto
impl CreateQueryToolDto
pub fn new(type: TypeTrue) -> CreateQueryToolDto
Trait Implementations§
Source§impl Clone for CreateQueryToolDto
impl Clone for CreateQueryToolDto
Source§fn clone(&self) -> CreateQueryToolDto
fn clone(&self) -> CreateQueryToolDto
1.0.0 · Source§const fn clone_from(&mut self, source: &Self)
const fn clone_from(&mut self, source: &Self)
source
. Read more