ed89af4b4d
# Backwards-compatible refactoring of the Slack toolkit Several performance improvements, streamlined tool set, and easier to understand tool interfaces. All "old" tools were kept for backwards compatibility, with the same interfaces and response structure (but using the new and more performant tools under the hood). Full revision of unit-tests and evals. ## Streamlined tool set Multiple groups of tools were streamlined into a single one: * "get conversation metadata" from 5 tools to one; * "send message" from 2 tools to one; * "get users in conversation" from 3 tools to one; * "get messages" from 4 tools to one ## New capabilities * Messages retrieved are now populated with the users' names, apart from ID: makes it easier for LLMs to reference who sent a message, were mentioned, or reacted to a message * Retrieve users by username, email, and/or ID (before we only supported ID) * Retrieve multiple users in a single tool call ## Concurrency controls All operations issuing multiple requests concurrently now have a `Semaphore` to limit the concurrency level. The limit can be controlled through the `SLACK_MAX_CONCURRENT_REQUESTS` env var (defaults to 3). ## Networking performance improvement Various operations that used to make multiple API calls are now executed more efficiently: ### Find users by username * Before: a full scan of `users_list` was required (potentially multiple pages for large workspaces); * Now it stops as soon as we have all users needed (yes, it was dumb before) ### Get multiple users by their IDs * Before: for each user ID, we made one API call to the `users_info` endpoint * Now: we call `list_users` and scan the results to match the user IDs (an estimate of 99.5% of Slack workspaces have < 200 users; for large workspaces, we may need to paginate `list_users`) ### Get a conversation by its users * Before: * Call to `list_conversations` (potentially paginating) * For each conversation, one call to `conversations_members` (potentially paginating) * Then loop and find which conversation matches the users' IDs * Now: * A single call to `conversations_open`
54 lines
2.1 KiB
Python
54 lines
2.1 KiB
Python
import base64
|
|
import json
|
|
from typing import Annotated
|
|
|
|
from arcade_tdk import ToolContext, ToolMetadataKey, tool
|
|
from arcade_tdk.auth import Google
|
|
from arcade_tdk.errors import ToolExecutionError
|
|
|
|
|
|
@tool(
|
|
requires_auth=Google(),
|
|
requires_metadata=[ToolMetadataKey.CLIENT_ID, ToolMetadataKey.COORDINATOR_URL],
|
|
)
|
|
def generate_google_file_picker_url(
|
|
context: ToolContext,
|
|
) -> Annotated[dict, "Google File Picker URL for user file selection and permission granting"]:
|
|
"""Generate a Google File Picker URL for user-driven file selection and authorization.
|
|
|
|
This tool generates a URL that directs the end-user to a Google File Picker interface where
|
|
where they can select or upload Google Drive files. Users can grant permission to access their
|
|
Drive files, providing a secure and authorized way to interact with their files.
|
|
|
|
This is particularly useful when prior tools (e.g., those accessing or modifying
|
|
Google Docs, Google Sheets, etc.) encountered failures due to file non-existence
|
|
(Requested entity was not found) or permission errors. Once the user completes the file
|
|
picker flow, the prior tool can be retried.
|
|
"""
|
|
client_id = context.get_metadata(ToolMetadataKey.CLIENT_ID)
|
|
client_id_parts = client_id.split("-")
|
|
if not client_id_parts:
|
|
raise ToolExecutionError(
|
|
message="Invalid Google Client ID",
|
|
developer_message=f"Google Client ID '{client_id}' is not valid",
|
|
)
|
|
app_id = client_id_parts[0]
|
|
cloud_coordinator_url = context.get_metadata(ToolMetadataKey.COORDINATOR_URL).strip("/")
|
|
|
|
config = {
|
|
"auth": {
|
|
"client_id": client_id,
|
|
"app_id": app_id,
|
|
},
|
|
}
|
|
config_json = json.dumps(config)
|
|
config_base64 = base64.urlsafe_b64encode(config_json.encode("utf-8")).decode("utf-8")
|
|
url = f"{cloud_coordinator_url}/google/drive_picker?config={config_base64}"
|
|
|
|
return {
|
|
"url": url,
|
|
"llm_instructions": (
|
|
"Instruct the user to click the following link to open the Google Drive File Picker. "
|
|
f"This will allow them to select files and grant access permissions: {url}"
|
|
),
|
|
}
|