@typia/website
    Preparing search index...
    IOptions: ModelConfig[Model] & {
        equals?: boolean;
        maxLength?: number;
        separate?: null | ((schema: ModelSchema[Model]) => boolean);
    }

    Options for the HTTP LLM application schema composition.

    Type Parameters

    Type Declaration

    • Optionalequals?: boolean

      Whether to disallow superfluous properties or not.

    • OptionalmaxLength?: number

      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).

      64
      
    • Optionalseparate?: null | ((schema: ModelSchema[Model]) => boolean)

      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 IGeminiSchema.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.

      • ILlmFunction.separated.llm
      • ILlmFunction.separated.human

      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 GeminiTypeChecker like features.

      null
      

      Schema to be separated.

      Whether the schema value must be composed by human or not.