[FEATURE] Configurable MCP Retry-ability

[dbschmigelski]

Problem Statement

The MCP client lacks a retry mechanism to allow tools/prompts to be retried without going back to the LLM. This is expensive, regarding time and financial cost.

Proposed Solution

Strands should not be opinionated in this regard. Many tools will not be retry-able or only in certain conditions. Instead, we should allow the customer to provide a retry strategy. This retry strategy can be applied to the MCPClient as a whole, as well as per tool.

Use Case

As a user, I would like to configure my MCP retry strategy.

Alternatives Solutions

No response

Additional Context

No response

[liushang1997]

Hi @dbschmigelski, I'm interested in addressing this issue.

[dbschmigelski]

Hey, sorry for the significant delay on this. We just introduced a new retry mechanism through Hooks for model invocations. Instead of the approach you currently have, what I think we are going to attempt to do, is provide a more general purpose Tool retry mechanism so we can address the problem for both MCP and non-mcp tools

[dbschmigelski]

After #1556 is merged we will work on adding something similar to ModelRetryStrategy but for tools.