Docs: Update Tool Error Handling #438
Open
+214
−40
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 GitHub.
|
EricGustin
changed the title
evantahler
requested changes
Sep 11, 2025
There was a problem hiding this comment.
This is good, but I think we are missing 2 things:
- How do you make your own error adapter? It might be enough just to link to the class in the TDK for now
- How should clients use the new error types? This page is for tool developers - we need a section on how, for example, to see that it's a rate limit and I need to wait 20s before trying again
|
|
||
| @tool( | ||
| requires_auth=Google(scopes=["https://www.googleapis.com/auth/gmail.readonly"]), | ||
| error_adapters=[GoogleErrorAdapter] |
There was a problem hiding this comment.
Suggested change
| error_adapters=[GoogleErrorAdapter] | |
| error_adapters=[GoogleErrorAdapter] # note the tool opts-into the error adapter |
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.
This doc is targeted to tool developers and is about how and when to raise errors in your tools.
When writing this up I noticed that our documentation is missing a "Using Tools" section. Within that section we could talk about how to properly catch errors when calling tools via the client libraries.