Show / Hide Table of Contents

Class ConversationArgs

Arguments to be used for LLM conversation.

Inheritance
object
ConversationArgs
Inherited Members
object.Equals(object)
object.Equals(object, object)
object.GetHashCode()
object.GetType()
object.MemberwiseClone()
object.ReferenceEquals(object, object)
object.ToString()
Namespace: Quantellia.WMServer.Asset.LLM
Assembly: WMServer.dll
Syntax
public class ConversationArgs

Properties

ConversationID

An ID specifying an ongoing conversation. If null or unspecified, create a new conversation.

Declaration
public string? ConversationID { get; set; }
Property Value
Type Description
string

FilterType

How the optional supplied tags should be used to filter (RAG) context.

Declaration
public string FilterType { get; set; }
Property Value
Type Description
string

Format

Potential strings to specify formatting.

Declaration
public string Format { get; set; }
Property Value
Type Description
string

LLM

An ID or fullPathName specifying the LLM asset to use in this conversation.

Declaration
public string LLM { get; set; }
Property Value
Type Description
string

Message

The message provided.

Declaration
public string Message { get; set; }
Property Value
Type Description
string

Paginate

If true, the response will be divided into multiple requests and responses under the ILLM's token limit. If false, a large request may error due to being over the token limit. Supported Formats: json: Each of the json responses will be combined to a single json with the recursive union of every property in each response. Duplicate properties will be ordered by occurrence of value and the first on the stack selected. i.e. if two responses have data.user.name = "Jerry" and one has data.user.name = "Jim" "Jerry" will be the preferred value for data.user.name in the combined json. Arrays will be concatenated. Typing mismatch will result in an error. markdown plaintext none: Responses will be appended to one another. Caution should be taken with prompts that prompt the LLM to return a header or title.

Unsupported Formats: html: Because there is no html schema validation, there is no way to determine whether a response is valid html, nor is there a trivial way to combine html like there is json.

Declaration
public bool Paginate { get; set; }
Property Value
Type Description
bool

Schema

Potential additional specifications to formatting.

Declaration
public string Schema { get; set; }
Property Value
Type Description
string

Tags

Optional tags used to filter (RAG) context.

Declaration
public List<string> Tags { get; set; }
Property Value
Type Description
List<string>
In this article
Back to top Copyright © 2025 Quantellia LLC.    Version 2.0.0 Revision 399     Last Updated 1/15/2025    DRAFT DOCUMENTATION. SUBJECT TO CHANGE