Repository navigation
Conversation
This branch has not been deployed
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
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
VikingBot previously reduced every exception from an outbound MCP
tools/callrequest to the exception class name. When a reachable server returned a JSON-RPC error for invalid arguments, the model saw onlyMcpErrorand lost the information needed to correct the call.JSON-RPC error answers now produce a bounded, credential-redacted result that includes the error code and server message. The MCP SDK's connection-closed and request-timeout codes remain on the existing transport-failure path.
Human Involvement
Related Issue
External evidence: NousResearch/hermes-agent#142864
Type of Change
Changes Made
Testing
Validation completed:
A source-pinned before/after probe ran twice per revision with byte-identical output. It verified that
-32603becomes actionable,-32000and-32001remain generic transport failures, malformed and ordinary exceptions retain their current result, and credential-shaped message content is redacted.Checklist
Screenshots (if applicable)
Not applicable.
Additional Notes
This change does not add retries, replay failed calls, open a circuit breaker, or alter MCP connection ownership.