pub struct GhlToolWithToolCall {
pub messages: Option<Vec<CreateDtmfToolDtoMessagesInner>>,
pub type: TypeTrue,
pub tool_call: ToolCall,
pub metadata: GhlToolMetadata,
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: TypeTrueThe type of tool. "ghl" for GHL tool.
tool_call: ToolCall§metadata: GhlToolMetadata§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 GhlToolWithToolCall
impl GhlToolWithToolCall
pub fn new( type: TypeTrue, tool_call: ToolCall, metadata: GhlToolMetadata, ) -> GhlToolWithToolCall
Trait Implementations§
Source§impl Clone for GhlToolWithToolCall
impl Clone for GhlToolWithToolCall
Source§fn clone(&self) -> GhlToolWithToolCall
fn clone(&self) -> GhlToolWithToolCall
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more