From 1855b649f1fe9adbb96800d122cebe858806b788 Mon Sep 17 00:00:00 2001 From: Travis Fischer Date: Tue, 18 Mar 2025 21:15:33 +0800 Subject: [PATCH] =?UTF-8?q?=E2=9A=92?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- legacy/readme.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/legacy/readme.md b/legacy/readme.md index ae1aaefb..e628be60 100644 --- a/legacy/readme.md +++ b/legacy/readme.md @@ -81,7 +81,7 @@ You can use our standard library of thoroughly tested AI functions with your fav ### Under the hood -All of the adapters (like `createAISDKTools` in this example) accept a very flexible var args of `AIFunctionLike` parameters, so you can pass as many tools / functions / clients as you like. An `AIFunctionLike` can be any agentic client instance, a single `AIFunction` selected from the client's `.functions` property (which holds an `AIFunctionSet` of available AI functions), or an AI function created manually via `createAIFunction`. +All of the adapters (like `createAISDKTools` in this example) accept a very flexible var args of `AIFunctionLike` parameters, so you can pass as many tools as you'd like. An `AIFunctionLike` can be any agentic client instance, a single `AIFunction` selected from the client's `.functions` property (which holds an `AIFunctionSet` of available AI functions), or an AI function created manually via `createAIFunction`. `AIFunctionLike` and `AIFunctionSet` are implementation details that you likely won't have to touch directly, but they're important primitives because they're designed to maximize flexibility when working with various AI functions coming from different places.