Add configurable retry policy for MCP tool resolution#170
Draft
paul-cayet wants to merge 1 commit into
Draft
Conversation
oracle-contributor-agreement
Bot
added
the
OCA Verified
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
#161
Adds optional tool_resolution_retry_policy support to MCPTool and MCPToolBox so clients can retry MCP
list_tools()resolution when expected tools are transiently missing from a partial server response.This keeps the default behavior unchanged: no retry is performed unless a retry policy is explicitly configured and WayFlow knows which tools are expected.
Changes include:
tool_resolution_retry_policy: Optional[RetryPolicy]to MCPTool and MCPToolBoxNoSuchToolFoundOnMCPServerErrorwith missing, expected, exposed tool names, and attempts