Improve generic 'Method not found' message for better debuggability

[alantriesagain]

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

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

[cliffhall]

LGTM! 👍

[changeset-bot]

⚠️ No Changeset found

Latest commit: bf45aa5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/client@955

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/server@955

commit: bf45aa5