Repository navigation
feat(mcp): auto-refresh and retry on Tool not found - #16
Merged
Merged
Conversation
When a tools/call returns isError with "Tool not found", fetch tools/list once and retry if the tool now appears. If it is still missing, fail with up to 5 did-you-mean suggestions ranked by shared underscore tokens.
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.
When
mcp tools-callgetsisError=truewith text startingTool not found, the CLI now callstools/listand retries once if the tool is now present. If still missing, it fails with up to 5 "did you mean" suggestions ranked by shared underscore tokens.Test plan
make testpasses (new tests forisToolNotFoundandsimilarTools)make buildpassespipeboard mcp tools-call --server snap-ads-mcp --tool list_snap_segments ...and confirm the retry path fires