Whether to allow reference type in everywhere.
If you configure this property to false, most of reference types
represented by ILlmSchema.IReference would be escaped to a plain
type unless recursive type comes.
This is because some LLM models do not understand the reference type well, and even the modern version of LLM sometimes occur the hallucination.
However, the reference type makes the schema size smaller, so that
reduces the LLM token cost. Therefore, if you're using the modern version
of LLM, and want to reduce the LLM token cost, you can configure this
property to true.
Separator function for the parameters.
When composing parameter arguments through LLM function call, there can be a case that some parameters must be composed by human, or LLM cannot understand the parameter.
For example, if the parameter type has configured ILlmSchema.IString.contentMediaType which indicates file uploading, it must be composed by human, not by LLM (Large Language Model).
In that case, if you configure this property with a function that predicating whether the schema value must be composed by human or not, the parameters would be separated into two parts.
When writing the function, note that returning value true means to be a
human composing the value, and false means to LLM composing the value.
Also, when predicating the schema, it would better to utilize the
LlmTypeChecker like features.
Whether to apply the strict mode.
If you configure this property to true, the LLM function calling does
not allow optional properties and dynamic key typed properties in the
ILlmSchema.IObject type. In other words, when strict mode is
enabled, ILlmSchema.IObject.additionalProperties is fixed to
false, and every property must be ILlmSchema.IObject.required.
However, the strict mode actually shows lower performance in practice. If you utilize the typia.validate function and give its validation feedback to the LLM, the performance is much better than the strict mode.
Therefore, I recommend you to just turn off the strict mode and utilize the typia.validate function instead.
Custom validation functions for specific class methods.
The validate property allows you to provide custom validation functions
that will replace the default validation behavior for specific methods
within the application class. When specified, these custom validators
take precedence over the standard type validation generated by
typia.llm.application().
This feature is particularly useful when you need to:
Each validation function receives the same arguments as its corresponding
method and must return an IValidation result. On validation
success, it should return { success: true, data }. On failure, it
should return { success: false, data, errors } with detailed error
information that helps AI agents understand and correct their mistakes.
Configuration for application composition.