Set IsError on CallToolResponse to true when result is ErrorContent #394
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.
Currently when providing an ErrorContent type as the result to a tool the IsError property on the resulting CallToolResponse is not set to true.
Motivation and Context
To allow the calling client to understand the response is an error the IsError property should be set to true when an error has occurred within the tool invocation. Unlike throwing an exception this can protect any potential unwanted information being reported from the exception details.
How Has This Been Tested?
Adjusted sample tools to confirm IsError is being set to true when an ErrorContent result is returned
Breaking Changes
No
Types of changes
Checklist
Additional context