Improve generic 'Method not found' message for better debuggability #955
+1
−1
Conversation
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
felixweinberger
force-pushed
the
main
branch
from
0845a57 to
c94ba4b
Compare
meiraleal
force-pushed
the
main
branch
3 times, most recently
from
4c9291b to
1b7f03e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation and Context
the message MCP error -32601: Method not found is too generic and don't help the user figure out what is wrong. So this PR adds the method to the message.
Changed to: MCP error -32601: Method 'elicitation/create' not found
How Has This Been Tested?
Tested in my fork, MCP inspector and local client
Breaking Changes
none
Types of changes
Checklist
Additional context