Keep MCP tool errors on the connection#218
Merged
Merged
Conversation
There was a problem hiding this comment.
Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.
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.
Upgrade Overview
Protected Areas
Compatibility Impact
This preserves the existing MCP tool response shape for known validation and policy errors while adding a defensive boundary for unexpected runtime failures. MCP clients should now receive a normal tool
isErrorresponse instead of losing the stdio connection when a backend dependency fails duringtools/call.Migration / Rollout
No migration is required. Restart any running Alice MCP server or connected agent process after deploying so it picks up the patched
mcp_server.py.Operator Action
After merge, restart the local Alice MCP server/agent and retry the memory commit. If the underlying issue is environmental, such as a database connection problem, the agent will now see a structured tool error instead of
MCP connection closed during the call.Validation
Validated locally with the targeted MCP unit suite, Python compile check, whitespace check, MCP stdio failure reproduction, and an MCP trusted commit plus undo smoke against local Postgres.
Rollback
Rollback is a normal revert of this PR. The change only affects MCP JSON-RPC error containment and does not alter memory data, schemas, or commit policy.
What Changed
tools/callJSON-RPC boundary.isErrortool result instead of letting the MCP server process terminate.Validation Evidence
Passed locally:
./.venv/bin/pytest tests/unit/test_mcp.py -q(15 passed)./.venv/bin/python -m py_compile apps/api/src/alicebot_api/mcp_server.pygit diff --checkisErrorinstead of crashing on an injected database connection failure.