Class: Vapi::FunctionToolWithToolCall

Inherits:
Object
  • Object
show all
Defined in:
lib/vapi_server_sdk/types/function_tool_with_tool_call.rb

Constant Summary collapse

OMIT = 
Object.new

Instance Attribute Summary collapse

Class Method Summary collapse

Instance Method Summary collapse

Constructor Details

#initialize(tool_call:, messages: OMIT, async: OMIT, server: OMIT, function: OMIT, additional_properties: nil) ⇒ Vapi::FunctionToolWithToolCall

Parameters:

  • messages (Array<Vapi::FunctionToolWithToolCallMessagesItem>) (defaults to: OMIT) —

    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.

  • async (Boolean) (defaults to: OMIT) —

    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`).

  • server (Vapi::Server) (defaults to: OMIT) —

    This is the server where a ‘tool-calls` webhook will be sent. Notes:

    • Webhook is sent to this server when a tool call is made.

    • Webhook contains the call, assistant, and phone number objects.

    • Webhook contains the variables set on the assistant.

    • Webhook is sent to the first available URL in this order:

    Vapi::FunctionToolWithToolCall.{tool{tool.server{tool.server.url}, Vapi::FunctionToolWithToolCall.{assistant{assistant.server{assistant.server.url}, Vapi::FunctionToolWithToolCall.{phoneNumber{phoneNumber.server{phoneNumber.server.url}, Vapi::FunctionToolWithToolCall.{org{org.server{org.server.url}.

    • Webhook expects a response with tool call result.

  • tool_call (Vapi::ToolCall)
  • function (Vapi::OpenAiFunction) (defaults to: OMIT) —

    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.

  • additional_properties (OpenStruct) (defaults to: nil) —

    Additional properties unmapped to the current class definition



87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
 
# File 'lib/vapi_server_sdk/types/function_tool_with_tool_call.rb', line 87

def initialize(tool_call:, messages: OMIT, async: OMIT, server: OMIT, function: OMIT, additional_properties: nil)
  @messages = messages if messages != OMIT
  @async = async if async != OMIT
  @server = server if server != OMIT
  @tool_call = tool_call
  @function = function if function != OMIT
  @additional_properties = additional_properties
  @_field_set = {
    "messages": messages,
    "async": async,
    "server": server,
    "toolCall": tool_call,
    "function": function
  }.reject do |_k, v|
    v == OMIT
  end
end

Instance Attribute Details

#additional_properties ⇒ OpenStruct (readonly)

Returns Additional properties unmapped to the current class definition.

Returns:

  • (OpenStruct) —

    Additional properties unmapped to the current class definition



48
49
50
 
# File 'lib/vapi_server_sdk/types/function_tool_with_tool_call.rb', line 48

def additional_properties
  @additional_properties
end

#async ⇒ Boolean (readonly)

Returns 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`).

Returns:

  • (Boolean) —

    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`).



23
24
25
 
# File 'lib/vapi_server_sdk/types/function_tool_with_tool_call.rb', line 23

def async
  @async
end

#function ⇒ Vapi::OpenAiFunction (readonly)

Returns 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.

Returns:

  • (Vapi::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.



46
47
48
 
# File 'lib/vapi_server_sdk/types/function_tool_with_tool_call.rb', line 46

def function
  @function
end

#messages ⇒ Array<Vapi::FunctionToolWithToolCallMessagesItem> (readonly)

Returns 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.

Returns:

  • (Array<Vapi::FunctionToolWithToolCallMessagesItem>) —

    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.



16
17
18
 
# File 'lib/vapi_server_sdk/types/function_tool_with_tool_call.rb', line 16

def messages
  @messages
end

#server ⇒ Vapi::Server (readonly)

Returns This is the server where a ‘tool-calls` webhook will be sent. Notes:

  • Webhook is sent to this server when a tool call is made.

  • Webhook contains the call, assistant, and phone number objects.

  • Webhook contains the variables set on the assistant.

  • Webhook is sent to the first available URL in this order:

Vapi::FunctionToolWithToolCall.{tool{tool.server{tool.server.url}, Vapi::FunctionToolWithToolCall.{assistant{assistant.server{assistant.server.url}, Vapi::FunctionToolWithToolCall.{phoneNumber{phoneNumber.server{phoneNumber.server.url}, Vapi::FunctionToolWithToolCall.{org{org.server{org.server.url}.

  • Webhook expects a response with tool call result.

Returns:

  • (Vapi::Server) —

    This is the server where a ‘tool-calls` webhook will be sent. Notes:

    • Webhook is sent to this server when a tool call is made.

    • Webhook contains the call, assistant, and phone number objects.

    • Webhook contains the variables set on the assistant.

    • Webhook is sent to the first available URL in this order:

    Vapi::FunctionToolWithToolCall.{tool{tool.server{tool.server.url}, Vapi::FunctionToolWithToolCall.{assistant{assistant.server{assistant.server.url}, Vapi::FunctionToolWithToolCall.{phoneNumber{phoneNumber.server{phoneNumber.server.url}, Vapi::FunctionToolWithToolCall.{org{org.server{org.server.url}.

    • Webhook expects a response with tool call result.



34
35
36
 
# File 'lib/vapi_server_sdk/types/function_tool_with_tool_call.rb', line 34

def server
  @server
end

#tool_call ⇒ Vapi::ToolCall (readonly)

Returns:



36
37
38
 
# File 'lib/vapi_server_sdk/types/function_tool_with_tool_call.rb', line 36

def tool_call
  @tool_call
end

Class Method Details

.from_json(json_object:) ⇒ Vapi::FunctionToolWithToolCall

Deserialize a JSON object to an instance of FunctionToolWithToolCall

Parameters:

  • json_object (String)

Returns:



109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
 
# File 'lib/vapi_server_sdk/types/function_tool_with_tool_call.rb', line 109

def self.from_json(json_object:)
  struct = JSON.parse(json_object, object_class: OpenStruct)
  parsed_json = JSON.parse(json_object)
  messages = parsed_json["messages"]&.map do |item|
    item = item.to_json
    Vapi::FunctionToolWithToolCallMessagesItem.from_json(json_object: item)
  end
  async = parsed_json["async"]
  if parsed_json["server"].nil?
    server = nil
  else
    server = parsed_json["server"].to_json
    server = Vapi::Server.from_json(json_object: server)
  end
  if parsed_json["toolCall"].nil?
    tool_call = nil
  else
    tool_call = parsed_json["toolCall"].to_json
    tool_call = Vapi::ToolCall.from_json(json_object: tool_call)
  end
  if parsed_json["function"].nil?
    function = nil
  else
    function = parsed_json["function"].to_json
    function = Vapi::OpenAiFunction.from_json(json_object: function)
  end
  new(
    messages: messages,
    async: async,
    server: server,
    tool_call: tool_call,
    function: function,
    additional_properties: struct
  )
end

.validate_raw(obj:) ⇒ Void

Leveraged for Union-type generation, validate_raw attempts to parse the given

hash and check each fields type against the current object's property
definitions.

Parameters:

  • obj (Object)

Returns:

  • (Void) 


158
159
160
161
162
163
164
 
# File 'lib/vapi_server_sdk/types/function_tool_with_tool_call.rb', line 158

def self.validate_raw(obj:)
  obj.messages&.is_a?(Array) != false || raise("Passed value for field obj.messages is not the expected type, validation failed.")
  obj.async&.is_a?(Boolean) != false || raise("Passed value for field obj.async is not the expected type, validation failed.")
  obj.server.nil? || Vapi::Server.validate_raw(obj: obj.server)
  Vapi::ToolCall.validate_raw(obj: obj.tool_call)
  obj.function.nil? || Vapi::OpenAiFunction.validate_raw(obj: obj.function)
end

Instance Method Details

#to_json(*_args) ⇒ String

Serialize an instance of FunctionToolWithToolCall to a JSON object

Returns:

  • (String) 


148
149
150
 
# File 'lib/vapi_server_sdk/types/function_tool_with_tool_call.rb', line 148

def to_json(*_args)
  @_field_set&.to_json
end