chore: enhance error messaging when MCP tools are used without sessio… #175
+8
−2
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
zastrowm
previously approved these changes
Jun 4, 2025
Co-authored-by: Mackenzie Zastrow <3211021+zastrowm@users.noreply.github.com>
awsarron
reviewed
Jun 4, 2025
zastrowm
approved these changes
Jun 9, 2025
3 tasks
15 tasks
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
Enhanced error messaging when MCP tools are used outside of the client context manager. This change improves the developer experience by providing more descriptive error messages that guide users on proper usage.
Problem: When MCP tools are used outside of the client context manager (with mcp_client:), the error message "the client session is not running" does not provide clear guidance on how to resolve the issue.
Solution: Updated the error message to explicitly indicate that the MCP client must be used within the context manager, making it easier for developers to identify and fix the issue.
Related Issues
Partially addresses #96 - STDIO MCP tool not working
Documentation PR
N/A
Type of Change
Testing
Yes.
hatch fmt --linterhatch fmt --formatterhatch test --allChecklist
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.