Skip to content

Commit 9123639

Browse files
committed
toolkit comes first
1 parent 646bc80 commit 9123639

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

pages/home/glossary.mdx

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,10 @@ graph TD
1818

1919
An 'agent' is the application you are building. It can be a chatbot, a web application, a mobile app, or any other type of application that happens to use an LLM to as part of its functionality. Agents interact with the world by calling tools. Helping you build, test, authenticate, and deploy tools is what Arcade is all about.
2020

21+
### Toolkit
22+
23+
A 'toolkit' is a collection of tools that can be used by an agent, grouped logically together by a common theme or provider. Toolkits are the unit of deployment for tools within Arcade.
24+
2125
### Tool
2226

2327
A 'tool' is a function that can be called by an agent which performs some action - commonly via an API, filesystem, database, etc. Tools are written in python and deployed by running a worker which contains the toolkit's code. Tools are defined by the `@tool()` decorator and will be passed `ToolContext` as the first argument. If a tool has dependencies that are not met (a secret is not provided, for example), the tool will fail to execute.
@@ -26,10 +30,6 @@ Tools are commonly referred to by a qualified name that includes their toolkit.
2630

2731
*Learn more about [tools](/home/build-tools/create-a-toolkit).*
2832

29-
### Toolkit
30-
31-
A 'toolkit' is a collection of tools that can be used by an agent, grouped logically together by a common theme or provider. Toolkits are the unit of deployment for tools within Arcade.
32-
3333
### Tool Context
3434

3535
'Tool context' is an object that is passed to a tool as a parameter when the tool is executed. It contains information about the tool call, the user for which the tool is being called, and any secrets the tool requires to run.

0 commit comments

Comments
 (0)