Class: Vapi::CreateMcpToolDto

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

Constant Summary collapse

OMIT = 
Object.new

Instance Attribute Summary collapse

Class Method Summary collapse

Instance Method Summary collapse

Constructor Details

#initialize(messages: OMIT, server: OMIT, metadata: OMIT, function: OMIT, additional_properties: nil) ⇒ Vapi::CreateMcpToolDto

Parameters:

  • messages (Array<Vapi::CreateMcpToolDtoMessagesItem>) (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.

  • 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::CreateMcpToolDto.{tool{tool.server{tool.server.url}, Vapi::CreateMcpToolDto.{assistant{assistant.server{assistant.server.url}, Vapi::CreateMcpToolDto.{phoneNumber{phoneNumber.server{phoneNumber.server.url}, Vapi::CreateMcpToolDto.{org{org.server{org.server.url}.

    • Webhook expects a response with tool call result.

  • metadata (Vapi::McpToolMetadata) (defaults to: OMIT)
  • 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



74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
 
# File 'lib/vapi_server_sdk/types/create_mcp_tool_dto.rb', line 74

def initialize(messages: OMIT, server: OMIT, metadata: OMIT, function: OMIT, additional_properties: nil)
  @messages = messages if messages != OMIT
  @server = server if server != OMIT
  @metadata = metadata if metadata != OMIT
  @function = function if function != OMIT
  @additional_properties = additional_properties
  @_field_set = {
    "messages": messages,
    "server": server,
    "metadata": metadata,
    "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



41
42
43
 
# File 'lib/vapi_server_sdk/types/create_mcp_tool_dto.rb', line 41

def additional_properties
  @additional_properties
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.



39
40
41
 
# File 'lib/vapi_server_sdk/types/create_mcp_tool_dto.rb', line 39

def function
  @function
end

#messages ⇒ Array<Vapi::CreateMcpToolDtoMessagesItem> (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::CreateMcpToolDtoMessagesItem>) —

    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/create_mcp_tool_dto.rb', line 16

def messages
  @messages
end

#metadata ⇒ Vapi::McpToolMetadata (readonly)

Returns:



29
30
31
 
# File 'lib/vapi_server_sdk/types/create_mcp_tool_dto.rb', line 29

def metadata
  @metadata
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::CreateMcpToolDto.{tool{tool.server{tool.server.url}, Vapi::CreateMcpToolDto.{assistant{assistant.server{assistant.server.url}, Vapi::CreateMcpToolDto.{phoneNumber{phoneNumber.server{phoneNumber.server.url}, Vapi::CreateMcpToolDto.{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::CreateMcpToolDto.{tool{tool.server{tool.server.url}, Vapi::CreateMcpToolDto.{assistant{assistant.server{assistant.server.url}, Vapi::CreateMcpToolDto.{phoneNumber{phoneNumber.server{phoneNumber.server.url}, Vapi::CreateMcpToolDto.{org{org.server{org.server.url}.

    • Webhook expects a response with tool call result.



27
28
29
 
# File 'lib/vapi_server_sdk/types/create_mcp_tool_dto.rb', line 27

def server
  @server
end

Class Method Details

.from_json(json_object:) ⇒ Vapi::CreateMcpToolDto

Deserialize a JSON object to an instance of CreateMcpToolDto

Parameters:

  • json_object (String)

Returns:



94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
 
# File 'lib/vapi_server_sdk/types/create_mcp_tool_dto.rb', line 94

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::CreateMcpToolDtoMessagesItem.from_json(json_object: item)
  end
  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["metadata"].nil?
    metadata = nil
  else
    metadata = parsed_json["metadata"].to_json
    metadata = Vapi::McpToolMetadata.from_json(json_object: metadata)
  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,
    server: server,
    metadata: metadata,
    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) 


141
142
143
144
145
146
 
# File 'lib/vapi_server_sdk/types/create_mcp_tool_dto.rb', line 141

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.server.nil? || Vapi::Server.validate_raw(obj: obj.server)
  obj.metadata.nil? || Vapi::McpToolMetadata.validate_raw(obj: obj.metadata)
  obj.function.nil? || Vapi::OpenAiFunction.validate_raw(obj: obj.function)
end

Instance Method Details

#to_json(*_args) ⇒ String

Serialize an instance of CreateMcpToolDto to a JSON object

Returns:

  • (String) 


131
132
133
 
# File 'lib/vapi_server_sdk/types/create_mcp_tool_dto.rb', line 131

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