Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improved tool documentation, explicit field for error, and error filtering #5267

Open
wistuba opened this issue Jan 30, 2025 · 1 comment
Open
Labels
Milestone

Comments

@wistuba
Copy link

wistuba commented Jan 30, 2025

What feature would you like to be added?

  1. Documentation currently describes only happy paths for tools. It is unclear how to deal with errors in tools. There is no mention that you can simply raise an exception.
  2. The FunctionExecutionResultMessage should have a field indicating that an error was raised (Somewhat related Enable ToolResult Type in Core/AgentChat #4725 )
  3. An option to catch only specific errors with the option to stop for others

Why is this needed?

  1. Avoids that everyone has to read the code
  2. Anthropic models have an explicit field to indicate tool errors
  3. Some exceptions indicate serious issues that make it useless to continue. At that point I'd like to stop.
@wistuba wistuba changed the title Improved tool documentatio, explicit field for error, and error filtering Improved tool documentation, explicit field for error, and error filtering Jan 30, 2025
@ekzhu ekzhu added this to the python-v0.4.x milestone Jan 30, 2025
@ekzhu
Copy link
Collaborator

ekzhu commented Jan 30, 2025

Thanks for the issue @wistuba. Would be great to address all of them. I have created sub issues for this one.

Would you like to address these issues? We are happy to help guide you through the way.

@ekzhu ekzhu added help wanted Extra attention is needed proj-core proj-agentchat labels Jan 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants