Struct UpdateComputerToolDto

pub struct UpdateComputerToolDto {
    pub async: Option<bool>,
    pub messages: Option<Vec<CreateDtmfToolDtoMessagesInner>>,
    pub sub_type: Option<SubType>,
    pub function: Option<Box<OpenAiFunction>>,
    pub server: Option<Box<Server>>,
    pub name: Option<Name>,
    pub display_width_px: Option<f64>,
    pub display_height_px: Option<f64>,
    pub display_number: Option<f64>,
}

Fields

async: Option<bool>

This determines if the tool is async. If async, the assistant will move forward without waiting for your server to respond. This is useful if you just want to trigger something on your server. If sync, the assistant will wait for your server to respond. This is useful if want assistant to respond with the result from your server. Defaults to synchronous (false).

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.

sub_type: Option<SubType>

The sub type of tool.

function: Option<Box<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.

server: Option<Box<Server>>

This is the server that will be hit when this tool is requested by the model. All requests will be sent with the call object among other things. You can find more details in the Server URL documentation. This overrides the serverUrl set on the org and the phoneNumber. Order of precedence: highest tool.server.url, then assistant.serverUrl, then phoneNumber.serverUrl, then org.serverUrl.

name: Option<Name>

The name of the tool, fixed to ‘computer’

display_width_px: Option<f64>

The display width in pixels

display_height_px: Option<f64>

The display height in pixels

display_number: Option<f64>

Optional display number

Implementations

impl UpdateComputerToolDto

pub fn new() -> UpdateComputerToolDto

Trait Implementations

impl Clone for UpdateComputerToolDto

fn clone(&self) -> UpdateComputerToolDto

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for UpdateComputerToolDto

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for UpdateComputerToolDto

fn default() -> UpdateComputerToolDto

Returns the “default value” for a type.

impl<'de> Deserialize<'de> for UpdateComputerToolDto

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl PartialEq for UpdateComputerToolDto

fn eq(&self, other: &UpdateComputerToolDto) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl Serialize for UpdateComputerToolDto

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.

impl StructuralPartialEq for UpdateComputerToolDto