declare required environment keys

[pelikhan]

Since most tools require some environment variables, it would be nice to add some kind of "env: string[]" entry to the function spec so that we can do a friendly check ahead of execution.

[transitive-bullshit]

I like the idea of declaratively exposing any required environment keys.

Keep in mind that most of these classes need to be constructed and verify their keys before being used as AI functions. calculator is an AIFunction whereas most of these are AIFunctionProvider classes which expose AIFunctionProvider.functions, and once they've been new'ed, they will have already had their required env vars validated (or bypassed these env vars by passing values directly).

import { WeatherClient } from '@agentic/weather'

const weather = new WeatherClient() // this is where the env var is currently checked
defTool(weather.functions.get('get_current_weather'))

$`What is the weather in SF?`

Happy to expose env vars to the function spec or AIFunction type itself, since the spec currently has the data passed to OpenAI directly, so if we added anything else there we'd have to strip it off before using spec w/ OpenAI.

What about adding something like an abstract static method to AIFunctionProvider which would declaratively expose any env var required to instantiate that class?

[transitive-bullshit]

Related to my example code above, I believe it could be useful to either add an adaptor to Agentic for GenAIScript to support Agentic's notion of AIFunctionLike objects (AIFunction | AIFunctionProvider | AIFunctionSet), which will make working with the majority of the clients easier.

What you have as I understand it as examples for GenAIScript's defTool will currently work for simple AIFunctions like calculator, but the majority are classes which may expose multiple functions.

Happy to discuss the best way to support these and interop with GenAIScript as cleanly as possible.

[pelikhan]

Related to my example code above, I believe it could be useful to either add an adaptor to Agentic for GenAIScript to support Agentic's notion of AIFunctionLike objects (AIFunction | AIFunctionProvider | AIFunctionSet), which will make working with the majority of the clients easier.

What you have as I understand it as examples for GenAIScript's defTool will currently work for simple AIFunctions like calculator, but the majority are classes which may expose multiple functions.

Happy to discuss the best way to support these and interop with GenAIScript as cleanly as possible.

Ha, I shall fix that.

[pelikhan]

I like the idea of declaratively exposing any required environment keys.

Keep in mind that most of these classes need to be constructed and verify their keys before being used as AI functions. calculator is an AIFunction whereas most of these are AIFunctionProvider classes which expose AIFunctionProvider.functions, and once they've been new'ed, they will have already had their required env vars validated (or bypassed these env vars by passing values directly).

import { WeatherClient } from '@agentic/weather'

const weather = new WeatherClient() // this is where the env var is currently checked
defTool(weather.functions.get('get_current_weather'))

$`What is the weather in SF?`

Happy to expose env vars to the function spec or AIFunction type itself, since the spec currently has the data passed to OpenAI directly, so if we added anything else there we'd have to strip it off before using spec w/ OpenAI.

What about adding something like an abstract static method to AIFunctionProvider which would declaratively expose any env var required to instantiate that class?

Static field sound good. I could recover it from the instance constructor.

[pelikhan]

I've updated support for the AIProvider types (tested on the weather tool) --> https://microsoft.github.io/genaiscript/guides/agentic-tools/#weather-example