Whether to disallow superfluous properties or not.
Maximum length of function name.
When a function name is longer than this value, it will be truncated.
If not possible to truncate due to the duplication, the function name would be modified to randomly generated (UUID v4).
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.
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.
Configuration for the HTTP LLM application schema composition.