Glossary #361
Merged
Glossary #361
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Pull Request Overview
This PR adds a comprehensive glossary of terms to the Arcade platform documentation to help users understand key concepts and terminology.
- Adds a new glossary page with detailed definitions organized into logical sections
- Includes visual diagrams using Mermaid to illustrate relationships between concepts
- Integrates the glossary into the documentation navigation structure
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| pages/home/glossary.mdx | Creates comprehensive glossary with definitions for agents, tools, platform concepts, authentication, and billing terms |
| pages/home/_meta.tsx | Adds glossary entry to the documentation navigation menu |
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
jottakka
approved these changes
Jul 23, 2025
EricGustin
reviewed
Jul 23, 2025
EricGustin
reviewed
Jul 23, 2025
|
|
||
| ### Tool Executions | ||
|
|
||
| A 'tool execution' is a single call to a tool to interact with a remote system or service. The tool execution itself may fail (e.g. the user does not have permission to call the tool), but as long as the execution was able to be routed to a worker, the tool execution will be counted. |
There was a problem hiding this comment.
In my opinion it seems unfair to charge a customer for a tool execution if one of our official tools fail because of a KeyError, for example. This would be our fault and not theirs. For now though we don't have the ability determine if the tool execution failure is ours or not 🙂
nbarbettini
reviewed
Jul 23, 2025
nbarbettini
reviewed
Jul 23, 2025
nbarbettini
reviewed
Jul 23, 2025
EricGustin
reviewed
Jul 23, 2025
nbarbettini
reviewed
Jul 23, 2025
Co-authored-by: Nate Barbettini <[email protected]>
Co-authored-by: Nate Barbettini <[email protected]>
Co-authored-by: Nate Barbettini <[email protected]>
nbarbettini
reviewed
Jul 23, 2025
nbarbettini
reviewed
Jul 23, 2025
Co-authored-by: Nate Barbettini <[email protected]>
Co-authored-by: Nate Barbettini <[email protected]>
nbarbettini
reviewed
Jul 23, 2025
nbarbettini
reviewed
Jul 23, 2025
nbarbettini
reviewed
Jul 23, 2025
nbarbettini
reviewed
Jul 23, 2025
nbarbettini
reviewed
Jul 23, 2025
Co-authored-by: Nate Barbettini <[email protected]>
Co-authored-by: Nate Barbettini <[email protected]>
Co-authored-by: Nate Barbettini <[email protected]>
torresmateo
reviewed
Jul 24, 2025
Co-authored-by: Mateo Torres <[email protected]>
Co-authored-by: Mateo Torres <[email protected]>
Co-authored-by: Mateo Torres <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Arcade needs a glossary of terms.