Improve JSON-RPC error handling with typed errors and response constructors #595
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.
Description
Enhances JSON-RPC error handling by adding typed sentinel errors and response constructors to improve error checking patterns and reduce code duplication.
Summary:
ErrMethodNotFound
,ErrInvalidParams
, etc.) witherrors.Is()
supportAsError()
method onJSONRPCErrorDetails
for converting to typed errorsNewJSONRPCErrorResponse
,NewJSONRPCResultResponse
) to eliminate repetitive struct constructionCloses: #593
Type of Change
Checklist
MCP Spec Compliance
Additional Information
This change enables cleaner error handling patterns in code which consumes the
mcp-go
library:It also reduces repetitive response construction throughout the transport layer with dedicated constructors.