If you have configured the IHttpLlmApplication.IOptions.separate
option, every parameters in the IHttpLlmFunction would be separated
into both human and LLM sides. In that case, you can merge these human and
LLM sides' parameters into one through HttpLlm.mergeParameters
before the actual LLM function call execution.
Additionally, if you have configured the
IHttpLlmApplication.IOptions.keyword as true, the number of
IHttpLlmFunction.parameters are always 1 and the first parameter
type is always ILlmSchemaV3.IObject. I recommend this option because
LLM can understand the keyword arguments more easily.
Convert OpenAPI document to LLM function calling application.
Converts OpenAPI document or migrated application to the LLM function calling application. Every API operations in the OpenAPI document are converted to the LLM function type, and they would be used for the LLM function calling.
If you have configured the IHttpLlmApplication.IOptions.separate option, every parameters in the IHttpLlmFunction would be separated into both human and LLM sides. In that case, you can merge these human and LLM sides' parameters into one through HttpLlm.mergeParameters before the actual LLM function call execution.
Additionally, if you have configured the IHttpLlmApplication.IOptions.keyword as
true, the number of IHttpLlmFunction.parameters are always 1 and the first parameter type is always ILlmSchemaV3.IObject. I recommend this option because LLM can understand the keyword arguments more easily.