You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> * The primary `ToolboxClient` is asynchronous and requires using `await` for
63
+
> - The primary `ToolboxClient` is asynchronous and requires using `await` for
63
64
> loading and invoking tools, as shown in most examples.
64
65
> * Asynchronous code needs to run within an event loop (e.g., using
65
66
> `asyncio.run()` or in an async framework). See the [Python `asyncio`
@@ -72,6 +73,7 @@ pip install toolbox-core
72
73
73
74
Here's a minimal example to get you started. Ensure your Toolbox service is
74
75
running and accessible.
76
+
75
77
```py
76
78
import asyncio
77
79
from toolbox_core import ToolboxClient
@@ -323,15 +325,18 @@ ensuring only authorized users or applications can invoke them, especially when
323
325
accessing sensitive data.
324
326
325
327
### When is Authentication Needed?
328
+
326
329
Authentication is configured per-tool within the Toolbox service itself. If a
327
330
tool you intend to use is marked as requiring authentication in the service, you
328
331
must configure the SDK client to provide the necessary credentials (currently
329
332
Oauth2 tokens) when invoking that specific tool.
330
333
331
334
### Supported Authentication Mechanisms
335
+
332
336
The Toolbox service enables secure tool usage through **Authenticated Parameters**. For detailed information on how these mechanisms work within the Toolbox service and how to configure them, please refer to [Toolbox Service Documentation - Authenticated Parameters](https://googleapis.github.io/genai-toolbox/resources/tools/#authenticated-parameters)
333
337
334
338
### Step 1: Configure Tools in Toolbox Service
339
+
335
340
First, ensure the target tool(s) are configured correctly in the Toolbox service
336
341
to require authentication. Refer to the [Toolbox Service Documentation -
337
342
Authenticated
@@ -434,9 +439,9 @@ fixed and will not be requested or modified by the LLM during tool use.
434
439
435
440
### Why Bind Parameters?
436
441
437
-
***Protecting sensitive information:**API keys, secrets, etc.
438
-
***Enforcing consistency:** Ensuring specific values for certain parameters.
439
-
***Pre-filling known data:** Providing defaults or context.
442
+
-**Protecting sensitive information:**API keys, secrets, etc.
443
+
-**Enforcing consistency:** Ensuring specific values for certain parameters.
444
+
-**Pre-filling known data:** Providing defaults or context.
440
445
441
446
> [!IMPORTANT]
442
447
> The parameter names used for binding (e.g., `"api_key"`) must exactly match the
0 commit comments